[ https://issues.apache.org/jira/browse/HDFS-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022458#comment-13022458 ]
Hudson commented on HDFS-1476: ------------------------------ Integrated in Hadoop-Hdfs-trunk #643 (See [https://builds.apache.org/hudson/job/Hadoop-Hdfs-trunk/643/]) > listCorruptFileBlocks should be functional while the name node is still in > safe mode > ------------------------------------------------------------------------------------ > > Key: HDFS-1476 > URL: https://issues.apache.org/jira/browse/HDFS-1476 > Project: Hadoop HDFS > Issue Type: Improvement > Components: name-node > Affects Versions: 0.23.0 > Reporter: Patrick Kling > Assignee: Patrick Kling > Fix For: 0.23.0 > > Attachments: HDFS-1476.2.patch, HDFS-1476.3.patch, HDFS-1476.4.patch, > HDFS-1476.5.patch, HDFS-1476.patch > > > This would allow us to detect whether missing blocks can be fixed using Raid > and if that is the case exit safe mode earlier. > One way to make listCorruptFileBlocks available before the name node has > exited from safe mode would be to perform a scan of the blocks map on each > call to listCorruptFileBlocks to determine if there are any blocks with no > replicas. This scan could be parallelized by dividing the space of block IDs > into multiple intervals than can be scanned independently. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira