[
https://issues.apache.org/jira/browse/HADOOP-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645226#action_12645226
]
Arun C Murthy commented on HADOOP-3217:
---------------------------------------
I messed up the commit msg, so the subversion commits are available here:
trunk: http://svn.apache.org/viewcvs?view=rev&rev=705420
branch-19: http://svn.apache.org/viewcvs?view=rev&rev=705422
branch-18: http://svn.apache.org/viewcvs?view=rev&rev=705423
branch-17: http://svn.apache.org/viewcvs?view=rev&rev=705426
> [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
>
> 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.
