elasticsearch/docs/reference/snapshot-restore
David Turner 92d13a3f7d
Introduce repository test kit/analyser (#67247)
Today we rely on blob stores behaving in a certain way so that they can be used
as a snapshot repository. There are an increasing number of third-party blob
stores that claim to be S3-compatible, but which may not offer a suitably
correct or performant implementation of the S3 API. We rely on somesubtle
semantics with concurrent readers and writers, but some blob stores may not
implement it correctly. Hitting a corner case in the implementation may be rare
in normal use, and may be hard to reproduce or to distinguish from an
Elasticsearch bug.

This commit introduces a new `POST /_snapshot/.../_analyse` API which exercises
the more problematic corners of the repository implementation looking for
correctness bugs and measures the details of the performance of the repository
under concurrent load.
2021-02-16 14:24:40 +00:00
..
apis Introduce repository test kit/analyser (#67247) 2021-02-16 14:24:40 +00:00
delete-snapshot.asciidoc [DOCS] Updating snapshot/restore pages to align with API changes (#59730) 2020-07-17 13:08:13 -04:00
index.asciidoc Further emphasise filesystem backups don't work (#67634) 2021-01-19 17:55:11 +00:00
monitor-snapshot-restore.asciidoc Remove Outdated Snapshot Docs (#61684) 2020-08-31 15:52:49 +02:00
register-repository.asciidoc Introduce repository test kit/analyser (#67247) 2021-02-16 14:24:40 +00:00
restore-snapshot.asciidoc Introduce "Feature States" for managing snapshots of system indices (#63513) 2021-02-11 11:55:14 -07:00
take-snapshot.asciidoc Introduce "Feature States" for managing snapshots of system indices (#63513) 2021-02-11 11:55:14 -07:00