hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3217) [HOD] Be less agressive when querying job status from resource manager.
Date Thu, 16 Oct 2008 11:30:45 GMT

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

Hemanth Yamijala commented on HADOOP-3217:
------------------------------------------

bq. There was a minor issue : when invalid tarball is specified with tarball option then ringmaster
failure occurs and return code is 5 while for 0.17.3 without patch, return code is 6 for the
same scenario.
I discussed this with Vinod and Suman offline. There has always been a timing issue in this
part of the code. The patch makes it more likely that 5 is returned in this case. Note that
both indicate a ringmaster failure. I think at this stage, it is OK to ignore this minor anomaly
for now.

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


Mime
View raw message