[
https://issues.apache.org/jira/browse/MAPREDUCE-6776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated MAPREDUCE-6776:
-------------------------------------
Resolution: Fixed
Hadoop Flags: Incompatible change,Reviewed
Fix Version/s: 3.0.0-alpha2
2.9.0
Release Note: The default value of
yarn.app.mapreduce.client.job.max-retries has been changed from 0 to 3. This
will help protect clients from failures that are transient. True failures may
take slightly longer now due to the retries.
Status: Resolved (was: Patch Available)
Thanks [~miklos.szeg...@cloudera.com] and everyone. Committed to trunk and
branch-2!
> 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
> Fix For: 2.9.0, 3.0.0-alpha2
>
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
