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
As of now, we cleanup unreferenced files whenever last write is performed by merge and it caused disk to get full and shard to fail. Incase some other operation performs the last write and caused disk to get 100% full and a merge is ongoing, merge will just get aborted and no cleanup will be performed. Since when closing the shard it is the other operation causing disk full and not segment merge.
Related component
Storage
To Reproduce
There is no specific way in which we can reproduce this issue. Got to know about this from a flaky test case. In order to specifically reproduce this, we need some way to allow the merge and some other operation to happen in parallel. It should be the other operation (other than merge) which should cause disk to go 100% full.
Expected behavior
Cleanup unreferenced files when any operation failed due to disk full.
Additional Details
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
As of now, we cleanup unreferenced files whenever last write is performed by merge and it caused disk to get full and shard to fail. Incase some other operation performs the last write and caused disk to get 100% full and a merge is ongoing, merge will just get aborted and no cleanup will be performed. Since when closing the shard it is the other operation causing disk full and not segment merge.
Related component
Storage
To Reproduce
There is no specific way in which we can reproduce this issue. Got to know about this from a flaky test case. In order to specifically reproduce this, we need some way to allow the merge and some other operation to happen in parallel. It should be the other operation (other than merge) which should cause disk to go 100% full.
Expected behavior
Cleanup unreferenced files when any operation failed due to disk full.
Additional Details
No response
The text was updated successfully, but these errors were encountered: