[
https://issues.apache.org/jira/browse/YARN-8360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16543601#comment-16543601
]
Eric Yang commented on YARN-8360:
---------------------------------
[~suma.shivaprasad] Thank you for the patch. If number_of_containers is
greater than 1 for a given component, yarn.service.container-failure.retry.max
applies to total count of the component rather than applying
yarn.service.container-failure.retry.max to each instance that should stay up.
This means if an application requires: 100 containers, in order for the
container to retry on failure that covers all instances,
yarn.service.container-failure.retry.max should set to 100 for every container
to have a chance to retry once. It is also possible for one container to fail,
and get retried 100 times. This logic seems a little odd. Would it be
possible to track retries count by instance?
> Yarn service conflict between restart policy and NM configuration
> ------------------------------------------------------------------
>
> Key: YARN-8360
> URL: https://issues.apache.org/jira/browse/YARN-8360
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn
> Reporter: Chandni Singh
> Assignee: Suma Shivaprasad
> Priority: Major
> Attachments: YARN-8360.1.patch
>
>
> For the below spec, the service will not stop even after container failures
> because of the NM auto retry properties :
> * "yarn.service.container-failure.retry.max": 1,
> * "yarn.service.container-failure.validity-interval-ms": 5000
> The NM will continue auto-restarting containers.
> {{fail_after 20}} fails after 20 seconds. Since the validity failure
> interval is 5 seconds, NM will auto restart the container.
> {code:java}
> {
> "name": "fail-demo2",
> "version": "1.0.0",
> "components" :
> [
> {
> "name": "comp1",
> "number_of_containers": 1,
> "launch_command": "fail_after 20",
> "restart_policy": "NEVER",
> "resource": {
> "cpus": 1,
> "memory": "256"
> },
> "configuration": {
> "properties": {
> "yarn.service.container-failure.retry.max": 1,
> "yarn.service.container-failure.validity-interval-ms": 5000
> }
> }
> }
> ]
> }
> {code}
> If {{restart_policy}} is NEVER, then the service should stop after the
> container fails.
> Since we have introduced, the service level Restart Policies, I think we
> should make the NM auto retry configurations part of the {{RetryPolicy}} and
> get rid of all {{yarn.service.container-failure.**}} properties. Otherwise it
> gets confusing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
