You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Hemanth Yamijala (JIRA)" <ji...@apache.org> on 2008/10/15 07:10:44 UTC

[jira] Updated: (HADOOP-3217) [HOD] Be less agressive when querying job status from resource manager.

     [ https://issues.apache.org/jira/browse/HADOOP-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hemanth Yamijala updated HADOOP-3217:
-------------------------------------

         Priority: Blocker  (was: Major)
    Fix Version/s: 0.20.0
                   0.19.0
                   0.18.2
                   0.17.3
         Assignee: Hemanth Yamijala

This is causing some issues in a production deployment. Will work on a fix asap.

> [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
>
>
> 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.