stack es snapshot repository-verify-integrity cli command
Auth required
elastic stack es snapshot repository-verify-integrity \
--repository <repository> \
[options]
Verify the repository integrity.
Behaviour flags:
--dry-run — validate all inputs and exit without performing any action
--repositorystringrequired-
The name of the snapshot repository.
Repeatable: pass
--repositorymultiple times to supply more than one value --blob-thread-pool-concurrencynumber- If
verify_blob_contentsistrue, this parameter specifies how many blobs to verify at once. --index-snapshot-verification-concurrencynumber- The maximum number of index snapshots to verify concurrently within each index verification.
--index-verification-concurrencynumber- The number of indices to verify concurrently.
The default behavior is to use the entire
snapshot_metathread pool. --max-bytes-per-secstring- If
verify_blob_contentsistrue, this parameter specifies the maximum amount of data that Elasticsearch will read from the repository every second. --max-failed-shard-snapshotsnumber- The number of shard snapshot failures to track during integrity verification, in order to avoid excessive resource usage. If your repository contains more than this number of shard snapshot failures, the verification will fail.
--meta-thread-pool-concurrencynumber- The maximum number of snapshot metadata operations to run concurrently.
The default behavior is to use at most half of the
snapshot_metathread pool at once. --snapshot-verification-concurrencynumber- The number of snapshots to verify concurrently.
The default behavior is to use at most half of the
snapshot_metathread pool at once. --verify-blob-contents- Indicates whether to verify the checksum of every data blob in the repository. If this feature is enabled, Elasticsearch will read the entire repository contents, which may be extremely slow and expensive.
--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)
--json-
output as JSON