6aaee8aa0a
* Repository Cleanup Endpoint (#43900) * Snapshot cleanup functionality via transport/REST endpoint. * Added all the infrastructure for this with the HLRC and node client * Made use of it in tests and resolved relevant TODO * Added new `Custom` CS element that tracks the cleanup logic. Kept it similar to the delete and in progress classes and gave it some (for now) redundant way of handling multiple cleanups but only allow one * Use the exact same mechanism used by deletes to have the combination of CS entry and increment in repository state ID provide some concurrency safety (the initial approach of just an entry in the CS was not enough, we must increment the repository state ID to be safe against concurrent modifications, otherwise we run the risk of "cleaning up" blobs that just got created without noticing) * Isolated the logic to the transport action class as much as I could. It's not ideal, but we don't need to keep any state and do the same for other repository operations (like getting the detailed snapshot shard status) |
||
|---|---|---|
| .. | ||
| cluster | ||
| discovery | ||
| indices | ||
| cluster.asciidoc | ||
| cross-cluster-search.asciidoc | ||
| discovery.asciidoc | ||
| gateway.asciidoc | ||
| http.asciidoc | ||
| indices.asciidoc | ||
| memcached.asciidoc | ||
| network.asciidoc | ||
| node.asciidoc | ||
| plugins.asciidoc | ||
| remote-clusters.asciidoc | ||
| snapshots.asciidoc | ||
| threadpool.asciidoc | ||
| thrift.asciidoc | ||
| transport.asciidoc | ||