HDDS-10296. orphan blocks during overwrite of key #6180
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
for key overwrite case, objectId is same. for deleted key, its suffixed with objectId to be unique. So for continuous create and delete same key, there is a possibility of overwrite deletedTable entry causing missing cleanup of blocks of previous key.
Also snapshot content remain orphan in case of overwrite in active db.
As fix for overwrite, a unique id is appended to key in deleted table to make it unique.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-10296
How was this patch tested?