mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-06-28 17:34:17 -04:00
33a71e3289
* Remove `es-test-dir` book-scoped variable * Remove `plugins-examples-dir` book-scoped variable * Remove `:dependencies-dir:` and `:xes-repo-dir:` book-scoped variables - In `index.asciidoc`, two variables (`:dependencies-dir:` and `:xes-repo-dir:`) were removed. - In `sql/index.asciidoc`, the `:sql-tests:` path was updated to fuller path - In `esql/index.asciidoc`, the `:esql-tests:` path was updated idem * Replace `es-repo-dir` with `es-ref-dir` * Move `:include-xpack: true` to few files that use it, remove from index.asciidoc
18 lines
945 B
Text
18 lines
945 B
Text
[[repeated-snapshot-failures]]
|
|
== Addressing repeated snapshot policy failures
|
|
|
|
Repeated snapshot failures are usually an indicator of a problem with your deployment. Continuous failures of automated
|
|
snapshots can leave a deployment without recovery options in cases of data loss or outages.
|
|
|
|
Elasticsearch keeps track of the number of repeated failures when executing automated snapshots. If an automated
|
|
snapshot fails too many times without a successful execution, the health API will report a warning. The number of
|
|
repeated failures before reporting a warning is controlled by the
|
|
<<slm-health-failed-snapshot-warn-threshold,`slm.health.failed_snapshot_warn_threshold`>> setting.
|
|
|
|
In the event that an automated {slm} policy execution is experiencing repeated failures, follow these steps to get more
|
|
information about the problem:
|
|
|
|
include::{es-ref-dir}/tab-widgets/troubleshooting/snapshot/repeated-snapshot-failures-widget.asciidoc[]
|
|
|
|
|
|
|