[
https://issues.apache.org/jira/browse/HDFS-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291061#comment-13291061
]
Hadoop QA commented on HDFS-3512:
---------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12531266/HDFS-3512.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed unit tests in
hadoop-hdfs-project/hadoop-hdfs.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/2613//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2613//console
This message is automatically generated.
> Delay in scanning blocks at DN side when there are huge number of blocks
> ------------------------------------------------------------------------
>
> Key: HDFS-3512
> URL: https://issues.apache.org/jira/browse/HDFS-3512
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: data-node
> Affects Versions: 2.0.1-alpha
> Reporter: suja s
> Assignee: amith
> Attachments: HDFS-3512.patch
>
>
> Block scanner maintains the full list of blocks at DN side in a map and there
> is no differentiation between the blocks which are already scanned and the
> ones not scanend. For every check (ie every 5 secs) it will pick one block
> and scan. There are chances that it chooses a block which is already scanned
> which leads to further delay in scanning of blcoks which are yet to be
> scanned.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
