mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-25 07:37:19 -04:00
e6b830e3b3
If Elasticsearch fails part-way through a multipart upload to S3 it will generally try and abort the upload, but it's possible that the abort attempt also fails. In this case the upload becomes _dangling_. Dangling uploads consume storage space, and therefore cost money, until they are eventually aborted. Earlier versions of Elasticsearch require users to check for dangling multipart uploads, and to manually abort any that they find. This commit introduces a cleanup process which aborts all dangling uploads on each snapshot delete instead. Closes #44971 Closes #101169 |
||
|---|---|---|
| .. | ||
| apis | ||
| cluster-index-compat.asciidoc | ||
| index.asciidoc | ||
| on-prem-repo-type.asciidoc | ||
| register-repository.asciidoc | ||
| repository-azure.asciidoc | ||
| repository-gcs.asciidoc | ||
| repository-read-only-url.asciidoc | ||
| repository-s3.asciidoc | ||
| repository-shared-file-system.asciidoc | ||
| repository-shared-settings.asciidoc | ||
| repository-source-only.asciidoc | ||
| restore-snapshot.asciidoc | ||
| take-snapshot.asciidoc | ||