[
https://issues.apache.org/jira/browse/HDDS-9683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Doroszlai updated HDDS-9683:
-----------------------------------
Fix Version/s: 1.4.1
> Containers belonging to decommissioning or decommissioned nodes, are counted
> as mis-replicated
> ----------------------------------------------------------------------------------------------
>
> Key: HDDS-9683
> URL: https://issues.apache.org/jira/browse/HDDS-9683
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Christos Bisias
> Assignee: Christos Bisias
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0, 1.4.1
>
>
> When a node is decommissioning, new replicas are being copied to other nodes.
> Once the replica copies have been made, then the node goes into decommission.
> After the copies are made, the container appears as mis-replicated due to the
> excessive replicas. These replicas are unavailable and the decommissioned
> node is expected to be stopped. For that reason, containers that belong to
> decommissioning or decommissioned nodes, shouldn't be counted as
> mis-replicated.
>
> Out of service states for a node are {*}DECOMMISSIONING, DECOMMISSIONED,
> ENTERING_MAINTENANCE, IN_MAINTENANCE{*}.
> A node in maintenance, isn't expected to be stopped and therefore, no replica
> copies are made to other nodes. Mis-replication on a node in maintenance, is
> the same as having mis-replication on a healthy and active node. We will
> filter only nodes in decommission.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
