[ https://issues.apache.org/jira/browse/MAPREDUCE-6776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15537035#comment-15537035 ]
Robert Kanter edited comment on MAPREDUCE-6776 at 9/30/16 8:51 PM: ------------------------------------------------------------------- Ya, looks like YARN-5377 is for {{TestQueuingContainerManager}}, so that's not related. LGTM +1 [~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 better). was (Author: rkanter): Ya, looks like YARN-5377 is for {{TestQueuingContainerManager}}, so that's not related. LGTM [~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 better). > 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: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org