[
https://issues.apache.org/jira/browse/HADOOP-5784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amareshwari Sriramadasu updated HADOOP-5784:
--------------------------------------------
Fix Version/s: 0.21.0
Status: Patch Available (was: Open)
test-patch result:
{noformat}
[exec] -1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] -1 tests included. The patch doesn't appear to include any new
or modified tests.
[exec] Please justify why no tests are needed for
this patch.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec]
[exec] +1 Eclipse classpath. The patch retains Eclipse classpath
integrity.
[exec]
[exec] +1 release audit. The applied patch does not increase the
total number of release audit warnings.
{noformat}
It is difficult to write unit test for this.
Tested the patch by running sort on 500 nodes with
mapred.heartbeats.in.second=200.
> The length of the heartbeat cycle should be configurable.
> ---------------------------------------------------------
>
> Key: HADOOP-5784
> URL: https://issues.apache.org/jira/browse/HADOOP-5784
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Reporter: Owen O'Malley
> Assignee: Amareshwari Sriramadasu
> Fix For: 0.21.0
>
> Attachments: patch-5784.txt
>
>
> Currently, the hearbeat cycle is set to (# nodes / 100) in seconds. This can
> be too long for clusters that need to run low latency jobs. We should make
> the number of heartbeats that should arrive a second configurable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
