[ 
https://issues.apache.org/jira/browse/HADOOP-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561429#action_12561429
 ] 

Hadoop QA commented on HADOOP-2649:
-----------------------------------

+1 overall.  Here are the results of testing the latest attachment 
http://issues.apache.org/jira/secure/attachment/12373724/configurableReplicationPeriod.patch
against trunk revision r614192.

    @author +1.  The patch does not contain any @author tags.

    javadoc +1.  The javadoc tool did not generate any warning messages.

    javac +1.  The applied patch does not generate any new compiler warnings.

    findbugs +1.  The patch does not introduce any new Findbugs warnings.

    core tests +1.  The patch passed core unit tests.

    contrib tests +1.  The patch passed contrib unit tests.

Test results: 
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1675/testReport/
Findbugs warnings: 
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1675/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: 
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1675/artifact/trunk/build/test/checkstyle-errors.html
Console output: 
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1675/console

This message is automatically generated.

> The ReplicationMonitor sleep period should be configurable
> ----------------------------------------------------------
>
>                 Key: HADOOP-2649
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2649
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>            Priority: Blocker
>             Fix For: 0.16.0
>
>         Attachments: configurableReplicationPeriod.patch, 
> configurableReplicationPeriod.patch
>
>
> The HDFS Namenode computes replication work for datanodes once every 3 
> seconds. This should be a configurable  value. On large clusters, there could 
> be many many blocks in the neededReplication queue and computing replication 
> work for datanodes once every 3 seconds might consume lots of CPU on namenode.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to