[
https://issues.apache.org/jira/browse/HADOOP-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640326#action_12640326
]
Hadoop QA commented on HADOOP-3217:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12392183/HADOOP-3217
against trunk revision 705215.
+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 tests are needed for this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 Eclipse classpath. The patch retains Eclipse classpath integrity.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3476/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3476/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3476/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3476/console
This message is automatically generated.
> [HOD] Be less agressive when querying job status from resource manager.
> -----------------------------------------------------------------------
>
> Key: HADOOP-3217
> URL: https://issues.apache.org/jira/browse/HADOOP-3217
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/hod
> Affects Versions: 0.16.2
> Reporter: Hemanth Yamijala
> Assignee: Hemanth Yamijala
> Priority: Blocker
> Fix For: 0.17.3, 0.18.2, 0.19.0, 0.20.0
>
> Attachments: HADOOP-3217, HADOOP-3217.patch.0.17,
> HADOOP-3217.patch.0.17, HADOOP-3217.patch.0.17
>
>
> After a job is submitted, HOD queries torque periodically until it finds the
> job to be running / completed (due to error). The initial rate of query is
> once every 0.5 seconds for 20 times, and then once every 10 seconds. This is
> probably a tad too aggressive as we find that Torque sometimes returns some
> odd errors under heavy load in the cluster (HADOOP-3216). It may be better to
> query at a more relaxed rate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
