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
Describe the bug
Currently during snapshot delete, deletion of unlinked shard level blob is single threaded using SNAPSHOT threadpool. Hence if there is huge number of unlinked shard level blob flies, it will take considerable amount of time to clean them.
Hence I propose to make unlinked shard level blob deletion multi threaded delete the same way we do for cleaning up of stale indices, to speedup the overall snapshot deletion process.
To Reproduce
Steps to reproduce the behavior:
Create an Index index1
ingest documents to index1
Create a snapshot (lets call it snapshot1)
Wait for snapshot snap1 to compete
ingest lots of document to index1
Create a new snapshot (lets call it snapshot2)
Wait for snapshot snap2 to compete
delete snap2
You will see deletion of unlinked shard level blobs are getting deleted in only one thread even though snapshot thread pool have lots of thread available
Expected behavior
Deletion of unlinked shard level blobs should be multithreaded to speedup overall snapshot deletion.
Host/Environment (please complete the following information):
OS: [e.g. iOS] CentOs
Version [e.g. 22] 8
The text was updated successfully, but these errors were encountered:
Describe the bug
Currently during snapshot delete, deletion of unlinked shard level blob is single threaded using SNAPSHOT threadpool. Hence if there is huge number of unlinked shard level blob flies, it will take considerable amount of time to clean them.
Hence I propose to make unlinked shard level blob deletion multi threaded delete the same way we do for cleaning up of stale indices, to speedup the overall snapshot deletion process.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Deletion of unlinked shard level blobs should be multithreaded to speedup overall snapshot deletion.
Host/Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: