hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Kanter (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6776) yarn.app.mapreduce.client.job.max-retries should have a more useful default
Date Fri, 30 Sep 2016 20:52:20 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-6776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15537035#comment-15537035

Robert Kanter commented on MAPREDUCE-6776:

Ya, looks like YARN-5377 is for {{TestQueuingContainerManager}}, so that's not related.


[~hitesh], are you sure this should count as an incompatible change?  I know, it changes a
default value, but it should be transparent to the caller (in fact, it should make things

> yarn.app.mapreduce.client.job.max-retries should have a more useful default
> ---------------------------------------------------------------------------
>                 Key: MAPREDUCE-6776
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6776
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 2.8.0
>            Reporter: Daniel Templeton
>            Assignee: Miklos Szegedi
>         Attachments: MAPREDUCE-6776.001.patch, MAPREDUCE-6776.002.patch, MAPREDUCE-6776.003.patch
> The default is 0, so any communication failure results in a client failure.  Oozie doesn't
like that.  If the RM is failing over and Oozie gets a communication failure, it assumes the
target job has failed.  I propose raising the default to something modest like 3 or 5.  The
default retry interval is 2s.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org

View raw message