[
https://issues.apache.org/jira/browse/HDDS-13914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated HDDS-13914:
-------------------------------
Parent: HDDS-13775
Issue Type: Sub-task (was: Improvement)
> Update check logic in DeletedBlockLogImpl.checkInadequateReplica
> ----------------------------------------------------------------
>
> Key: HDDS-13914
> URL: https://issues.apache.org/jira/browse/HDDS-13914
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Janus Chow
> Assignee: Janus Chow
> Priority: Major
> Labels: pull-request-available
>
> A issue found when there is decommissioning/ed datanodes in the cluster.
> Container #1 has 4 replicas, 1 on the to be removed DN. In current check
> logic, the container's health result is OK, but one replica sits on the to be
> removed DN, and it's not in the dnList to be checked with, so this container
> is marked skipped.
> This issue will cause SCM skipping all the containers resides on the
> decommissioned DNs, slowing down the deletion speed.
> This ticket is update the logic of this check, checking the health based on
> the filter result.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
