You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Hanisha Koneru (JIRA)" <ji...@apache.org> on 2018/09/07 18:15:00 UTC
[jira] [Updated] (HDDS-400) Check global replication state for
containers of dead node
[ https://issues.apache.org/jira/browse/HDDS-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hanisha Koneru updated HDDS-400:
--------------------------------
Summary: Check global replication state for containers of dead node (was: Check global replication state of the reported containers on SCM)
> Check global replication state for containers of dead node
> ----------------------------------------------------------
>
> Key: HDDS-400
> URL: https://issues.apache.org/jira/browse/HDDS-400
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: SCM
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Priority: Blocker
> Fix For: 0.2.1
>
> Attachments: HDDS-400.001.patch, HDDS-400.002.patch, HDDS-400.004.patch, HDDS-400.005.patch
>
>
> Current container replication handler compare the reported containers with the previous report. It handles over an under replicated state.
> But there is no logic to check the cluster-wide replication count. If a node is went down it won't be detected.
> For the sake of simplicity I would add this check to the ContainerReportHandler (as of now). So all the reported container should have enough replicas.
> We can check the performance implication with genesis, but as a first implementation I think it could be good enough.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org