[ https://issues.apache.org/jira/browse/HDFS-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14250452#comment-14250452 ]
Hadoop QA commented on HDFS-7430: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12687802/HDFS-7430.006.patch against trunk revision 9b4ba40. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 13 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. There were no new javadoc warning messages. {color:red}-1 eclipse:eclipse{color}. The patch failed to build with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in . Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/9060//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/9060//console This message is automatically generated. > Refactor the BlockScanner to use O(1) memory and use multiple threads > --------------------------------------------------------------------- > > Key: HDFS-7430 > URL: https://issues.apache.org/jira/browse/HDFS-7430 > Project: Hadoop HDFS > Issue Type: Improvement > Affects Versions: 2.7.0 > Reporter: Colin Patrick McCabe > Assignee: Colin Patrick McCabe > Attachments: HDFS-7430.002.patch, HDFS-7430.003.patch, > HDFS-7430.004.patch, HDFS-7430.005.patch, HDFS-7430.006.patch, memory.png > > > We should update the BlockScanner to use a constant amount of memory by > keeping track of what block was scanned last, rather than by tracking the > scan status of all blocks in memory. Also, instead of having just one > thread, we should have a verification thread per hard disk (or other volume), > scanning at a configurable rate of bytes per second. -- This message was sent by Atlassian JIRA (v6.3.4#6332)