You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, During snapshot deletion we asynchronously try to cleanup shard blobs by creating batches of 1000 blobs at a time. If the index is remote store enabled, we also release lock for each shard blob followed by remote store cleanup if index is already deleted from the cluster. If either release lock or remote store cleanup fails even for one shard, we end up skipping the cleanup of the entire batch.
Due to this, we end up calling release locks for the entire batch in the next run again. this can be optimized by skipping shard blob cleanup for only those shards for which release lock or remote store cleanup failed.
Related component
Storage:Snapshots
To Reproduce
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected behavior
During batch shard blob deletion, in cases of release lock or remote store cleanup failures, we should only skip deletion of shard blobs with failures.
Additional Details
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
OS: [e.g. iOS]
Version [e.g. 22]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
Currently, During snapshot deletion we asynchronously try to cleanup shard blobs by creating batches of 1000 blobs at a time. If the index is remote store enabled, we also release lock for each shard blob followed by remote store cleanup if index is already deleted from the cluster. If either release lock or remote store cleanup fails even for one shard, we end up skipping the cleanup of the entire batch.
OpenSearch/server/src/main/java/org/opensearch/repositories/blobstore/BlobStoreRepository.java
Lines 1135 to 1155 in 76ae14a
Due to this, we end up calling release locks for the entire batch in the next run again. this can be optimized by skipping shard blob cleanup for only those shards for which release lock or remote store cleanup failed.
Related component
Storage:Snapshots
To Reproduce
Expected behavior
During batch shard blob deletion, in cases of release lock or remote store cleanup failures, we should only skip deletion of shard blobs with failures.
Additional Details
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: