[
https://issues.apache.org/jira/browse/HDDS-14684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarveksha Yeshavantha Raju updated HDDS-14684:
----------------------------------------------
Status: Patch Available (was: Open)
> Allow deletion of empty quasi-closed containers
> -----------------------------------------------
>
> Key: HDDS-14684
> URL: https://issues.apache.org/jira/browse/HDDS-14684
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Sarveksha Yeshavantha Raju
> Assignee: Sarveksha Yeshavantha Raju
> Priority: Major
> Labels: pull-request-available
>
> We now support tracking a container again if a new replica shows up with a
> higher BCSID after all replicas were deleted
> (https://issues.apache.org/jira/browse/HDDS-14416). With this change, we can
> potentially delete empty quasi-closed containers from the system. Even if
> they were missing some blocks and a new replica shows up with those blocks,
> it would be tracked and replicated again. The potential downside is this
> could appear as if the system incorrectly deleted data. For example, if all
> quasi-closed replicas are missing a block and they go from empty to deleted
> and then a client reads the block, we will see the read happening from a
> deleted container instead of a quasi-closed container. We may need to figure
> out some way to trace this so we can differentiate this from a case where a
> container replica was incorrectly deleted.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
