[
https://issues.apache.org/jira/browse/MAPREDUCE-6776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15537287#comment-15537287
]
Hitesh Shah commented on MAPREDUCE-6776:
----------------------------------------
FWIW, I do agree that this is a useful behavioral change that makes sense to
push to branch-2 but might be better to call it out as incompatible but at the
same release note it carefully to indicate that it will improve user experience
and not have any detrimental impact apart from the retry delay in some edge
cases.
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
