stack es ccr follow cli command
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Preview
Preview
Stack
Preview
Preview
elastic stack es ccr follow \
--leader-index <leader-index> \
--remote-cluster <remote-cluster> \
--index <index> \
[options]
Create a follower.
Behaviour flags:
--dry-run — validate all inputs and exit without performing any action
--leader-indexstringrequired- The name of the index in the leader cluster to follow.
--remote-clusterstringrequired- The remote cluster containing the leader index.
--indexstringrequired- The name of the follower index.
--master-timeoutstring- Period to wait for a connection to the master node.
--wait-for-active-shardsstring- Specifies the number of shards to wait on being active before responding. This defaults to waiting on none of the shards to be active. A shard must be restored from the leader index before being active. Restoring a follower shard requires transferring all the remote Lucene segment files to the follower index.
--data-stream-namestring- If the leader index is part of a data stream, the name to which the local data stream for the followed index should be renamed.
--max-outstanding-read-requestsnumber- The maximum number of outstanding reads requests from the remote cluster.
--max-outstanding-write-requestsnumber- The maximum number of outstanding write requests on the follower.
--max-read-request-operation-countnumber- The maximum number of operations to pull per read from the remote cluster.
--max-read-request-sizestring- The maximum size in bytes of per read of a batch of operations pulled from the remote cluster.
--max-retry-delaystring- The maximum time to wait before retrying an operation that failed exceptionally. An exponential backoff strategy is employed when retrying.
--max-write-buffer-countnumber- The maximum number of operations that can be queued for writing. When this limit is reached, reads from the remote cluster will be deferred until the number of queued operations goes below the limit.
--max-write-buffer-sizestring- The maximum total bytes of operations that can be queued for writing. When this limit is reached, reads from the remote cluster will be deferred until the total bytes of queued operations goes below the limit.
--max-write-request-operation-countnumber- The maximum number of operations per bulk write request executed on the follower.
--max-write-request-sizestring- The maximum total bytes of operations per bulk write request executed on the follower.
--read-poll-timeoutstring- The maximum time to wait for new operations on the remote cluster when the follower index is synchronized with the leader index. When the timeout has elapsed, the poll for operations will return to the follower so that it can update some statistics. Then the follower will immediately attempt to read from the leader again.
--settingsstring- Settings to override from the leader index.
--error-trace- When set to
trueElasticsearch will include the full stack trace of errors when they occur. --filter-pathstring-
Comma-separated list of filters in dot notation which reduce the response returned by Elasticsearch.
Repeatable: pass
--filter-pathmultiple times to supply more than one value --human- When set to
truewill return statistics in a format suitable for humans. For example"exists_time": "1h"for humans and"exists_time_in_millis": 3600000for computers. When disabled the human readable values will be omitted. This makes sense for responses being consumed only by machines. --pretty- If set to
truethe returned JSON will be "pretty-formatted". Only use this option for debugging only. --input-filestring- path to a JSON file to use as command input
--dry-run- validate all inputs and exit without performing any action (preview changes without applying them)
--no-validate- skip input validation and send the request as-is
--output-fieldsstring- comma-separated list of fields to include in output (dot-notation supported)
--output-templatestring- Mustache-like template for custom text output (e.g. "{{id}}: {{name}}")
--json-
output as JSON