[
https://issues.apache.org/jira/browse/HADOOP-4103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676475#action_12676475
]
Suresh Srinivas commented on HADOOP-4103:
-----------------------------------------
1. NamenodeProtocol.getStats() method documentation needs to be updated about
the fourth stat that is being reported
2. DFSAdmin.java - remove space before {{:}} in {{"Missing Blocks (approx) :
"}}. Additionally is it a good idea to print number of corrupt blocks, pending
replication, scheduled replication and under replicated block counts in the
report? Currently what is printed in dfsadmin report is also printed in the
cluster summary on namenode web page. It may be a good idea to keep both of
them consistent.
3. FSNamesystem.java {{computeReplicationWork()}} move the added code block
that sets {{missingBlocksInCurIter, missingBlocksInPrevIter}} to zero, above
the comments preceding it.
Would this change be incompatible because of change in the output of dfsadmin
report command?
> Alert for missing blocks
> ------------------------
>
> Key: HADOOP-4103
> URL: https://issues.apache.org/jira/browse/HADOOP-4103
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.17.2
> Reporter: Christian Kunz
> Assignee: Raghu Angadi
> Attachments: HADOOP-4103.patch
>
>
> A whole bunch of datanodes became dead because of some network problems
> resulting in heartbeat timeouts although datanodes were fine.
> Many processes started to fail because of the corrupted filesystem.
> In order to catch and diagnose such problems faster the namenode should
> detect the corruption automatically and provide a way to alert operations. At
> the minimum it should show the fact of corruption on the GUI.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
