[
https://issues.apache.org/jira/browse/HDDS-10296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated HDDS-10296:
-------------------------------
Target Version/s: 2.0.0, 1.4.2
> orphan blocks during overwrite of key
> -------------------------------------
>
> Key: HDDS-10296
> URL: https://issues.apache.org/jira/browse/HDDS-10296
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone Manager
> Reporter: Sumit Agrawal
> Assignee: Sumit Agrawal
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.0.0
>
>
> Overrite key behavior: When key is created again for existing key, its
> overwrite, as part of this,
> # ObjectId is same for previous key and new key going to be written
> # If versioning enabled (currently no support but code is present), add old
> blocks for versioning case with the key
> Problem observed:
> # In case of delete of same key (when previous key also present in deleted
> table), this will cause overwrite of key (as deleted table's key name is as
> objectId is same)
>
> As solution,
> # generate unique key for deleted table for overwrite cases
>
> While test, its observed that one of block remains orphan, and that is not
> being notified to delete to DN from logs. So above are possible scenario
> where blocks are not being tracked from code review perspective.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
