mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-25 07:37:19 -04:00
92d13a3f7d
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. |
||
|---|---|---|
| .. | ||
| clean-up-repo-api.asciidoc | ||
| clone-snapshot-api.asciidoc | ||
| create-snapshot-api.asciidoc | ||
| delete-repo-api.asciidoc | ||
| delete-snapshot-api.asciidoc | ||
| get-repo-api.asciidoc | ||
| get-snapshot-api.asciidoc | ||
| get-snapshot-status-api.asciidoc | ||
| get-snapshottable-features-api.asciidoc | ||
| put-repo-api.asciidoc | ||
| repo-analysis-api.asciidoc | ||
| restore-snapshot-api.asciidoc | ||
| snapshot-restore-apis.asciidoc | ||
| verify-repo-api.asciidoc | ||