[
https://issues.apache.org/jira/browse/YARN-8710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16646884#comment-16646884
]
Hudson commented on YARN-8710:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #15180 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/15180/])
YARN-8710. Service AM should set a finite limit on NM container max (billie:
rev aeeb0389a58bf6bb4857bc0f246a63a4bd018d51)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-services/hadoop-yarn-services-core/src/main/java/org/apache/hadoop/yarn/service/conf/YarnServiceConf.java
> Service AM should set a finite limit on NM container max retries
> -----------------------------------------------------------------
>
> Key: YARN-8710
> URL: https://issues.apache.org/jira/browse/YARN-8710
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn-native-services
> Reporter: Suma Shivaprasad
> Assignee: Suma Shivaprasad
> Priority: Major
> Fix For: 3.3.0
>
> Attachments: YARN-8710.1.patch, YARN-8710.2.patch
>
>
> Container retries are currently set to a default of -1 in
> AbstractProviderService.buildContainerRetry. If this is not overridden via
> service spec with a finite value for yarn.service.container-failure.retry.max
> , this causes infinite NM reties for the container for ALWAYS/ON_FAILURE
> restart policy . Ideally it should try a finite number of time on the same NM
> and subsequently Service AM can retry on another node.
> We can set this to default value of 3.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
