hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinayakumar B (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9258) NN should indicate which nodes are stale
Date Thu, 04 Feb 2016 13:27:39 GMT

    [ https://issues.apache.org/jira/browse/HDFS-9258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132310#comment-15132310

Vinayakumar B commented on HDFS-9258:

What is the difference of moving {{isStale()}} call to DatanodeManager..? Still DM checks
DatanodeDescriptor#isStale(..) itself right?

> NN should indicate which nodes are stale
> ----------------------------------------
>                 Key: HDFS-9258
>                 URL: https://issues.apache.org/jira/browse/HDFS-9258
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>    Affects Versions: 2.0.0-alpha
>            Reporter: Daryn Sharp
>            Assignee: Kuhu Shukla
>         Attachments: HDFS-9258-v1.patch, HDFS-9258-v2.patch
> Determining why the NN is not coming out of safemode is difficult - is it a bug or pending
block reports?  If the number of nodes appears sufficient, but there are missing blocks, it
would be nice to know which nodes haven't block reported (stale).  Instead of forcing the
NN to leave safemode prematurely, the SE can first force block reports from stale nodes.
> The datanode report and the web ui's node list should contain this information.

This message was sent by Atlassian JIRA

View raw message