[
https://issues.apache.org/jira/browse/HDFS-14649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16983127#comment-16983127
]
Hudson commented on HDFS-14649:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #17701 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/17701/])
HDFS-14649. Add suspect probe for DeadNodeDetector. Contributed by (yqlin: rev
c8bef4d6a6d7d5affd00cff6ea4a2e2ef778050e)
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/main/resources/hdfs-default.xml
* (edit)
hadoop-hdfs-project/hadoop-hdfs-client/src/main/java/org/apache/hadoop/hdfs/DeadNodeDetector.java
* (edit)
hadoop-hdfs-project/hadoop-hdfs-client/src/main/java/org/apache/hadoop/hdfs/client/HdfsClientConfigKeys.java
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestDeadNodeDetection.java
> Add suspect probe for DeadNodeDetector
> --------------------------------------
>
> Key: HDFS-14649
> URL: https://issues.apache.org/jira/browse/HDFS-14649
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Lisheng Sun
> Assignee: Lisheng Sun
> Priority: Major
> Fix For: 3.3.0
>
> Attachments: HDFS-14649.001.patch, HDFS-14649.002.patch,
> HDFS-14649.003.patch, HDFS-14649.004.patch, HDFS-14649.005.patch
>
>
> Add suspect probe for DeadNodeDetector.
> when some DataNode of the block is found to inaccessible, put the DataNode
> into it will be placed in the Suspicious Node list. Because when DataNode is
> not accessible, it is likely that the replica has been removed from the
> DataNode.Therefore, it needs to be confirmed by re-probing and requires a
> higher priority processing.
> And when DataNode is placed in the Suspicious Node list, it is accessed by
> other dfsinputstream.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
