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

Posted to mapreduce-issues@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2009/10/19 20:17:59 UTC

[jira] Updated: (MAPREDUCE-1120) JobClient poll intervals should be job configurations, not cluster configurations

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

Todd Lipcon updated MAPREDUCE-1120:
-----------------------------------

    Attachment: mapreduce-1120.txt

Trivial patch. To test, I ran TestTaskFail which uses this functionality, and verified that it's still polling quickly instead of sleeping (that testcase was setting the config in both the job and the cluster)

> JobClient poll intervals should be job configurations, not cluster configurations
> ---------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1120
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1120
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>            Priority: Minor
>         Attachments: mapreduce-1120.txt
>
>
> Job.waitForCompletion gets the poll interval from the Cluster object's configuration rather than its own Job configuration. This is counter-intuitive - Chris and I both made this same mistake working on MAPREDUCE-64, and Aaron agrees as well.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.