[ https://issues.apache.org/jira/browse/HDDS-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16607471#comment-16607471 ]
Hanisha Koneru commented on HDDS-400: ------------------------------------- Thanks [~elek] for working on this and [~ajayydv] and [~nandakumar131] for the reviews. Committed to trunk. > 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. > ----- After Jira discussion below, the final patch does the following: ----- > When a dead node is reported, the DeadNodeHandler checks the replication > state for all the containers in that node and fires replication events in > case of under/over-replicated blocks. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org