[
https://issues.apache.org/jira/browse/HDFS-9258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kuhu Shukla updated HDFS-9258:
------------------------------
Attachment: HDFS-9258-v1.patch
Added isStale to jmx info. Added an {{isStale()}} call to be on DNInfo and
replaced the old one where ever it was possible. Also
{{chooseDatanodesForCaching()}} was a static call which is called only once
from {{addNewPendingCached()}} which is non-static. Hence moving
chooseDatanodesForCaching to non-static method.
> 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
>
>
> 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
(v6.3.4#6332)
