[
https://issues.apache.org/jira/browse/HDDS-10296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Agrawal updated HDDS-10296:
---------------------------------
Description:
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.
was:
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:
# When old key info is retrieved and versioning is false, it will cleanup the
block list. But problem is when before cache is flushed to db for previous key,
it will cleanup that information from memory. and Hence, previous key is
written without any blocks.
# 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,
# need use copy of keyInfo when reusing previous key info, to avoid update
cache
# 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.
> 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
>
> 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]
