You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Nanda kumar (Jira)" <ji...@apache.org> on 2020/09/28 04:42:00 UTC
[jira] [Updated] (HDDS-4263) ReplicatiomManager shouldn't consider
origin node Id for CLOSED containers.
[ https://issues.apache.org/jira/browse/HDDS-4263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nanda kumar updated HDDS-4263:
------------------------------
Summary: ReplicatiomManager shouldn't consider origin node Id for CLOSED containers. (was: ReplicatiomManager shouldn't retain one healthy replica per origin node Id.)
> ReplicatiomManager shouldn't consider origin node Id for CLOSED containers.
> ---------------------------------------------------------------------------
>
> Key: HDDS-4263
> URL: https://issues.apache.org/jira/browse/HDDS-4263
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: SCM
> Affects Versions: 1.0.0
> Reporter: maobaolong
> Assignee: maobaolong
> Priority: Major
> Labels: pull-request-available
>
> ReplicationManager now retain one healthy replica for per origin node id, so if there are 5 replicas and all of them are birth in different node, replicatiomManager won't reduce the replica for this container.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org