You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/05/17 10:32:00 UTC
[jira] [Updated] (HDDS-5235) Recon counts deleted containers to
missing containers
[ https://issues.apache.org/jira/browse/HDDS-5235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HDDS-5235:
---------------------------------
Labels: pull-request-available (was: )
> Recon counts deleted containers to missing containers
> -----------------------------------------------------
>
> Key: HDDS-5235
> URL: https://issues.apache.org/jira/browse/HDDS-5235
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Janus Chow
> Assignee: Janus Chow
> Priority: Major
> Labels: pull-request-available
>
> When a container is deleted, SCM has ReplicationManager to check if the container is empty, then set container's state to DELETING, then DELETED.
> While Recon doesn't have ReplicationManager for this work, then ContainerHealthTask finds the replica of the deleted container is 0 and mark the container as MISSING.
> The bug can be reproduced by creating some big keys with Freon and then delete them.
> This ticket is for adding some prechecks for ContaienrHealthTask before setting a container to MISSING state.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org