You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@slider.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/10/12 00:55:00 UTC

[jira] [Commented] (SLIDER-1233) Lost nodes should not contribute to container failures

    [ https://issues.apache.org/jira/browse/SLIDER-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201292#comment-16201292 ] 

ASF subversion and git services commented on SLIDER-1233:
---------------------------------------------------------

Commit 720bd19df9d2c0ad74cd536802a3c0028f7cfa96 in incubator-slider's branch refs/heads/develop from [~gsaha]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=720bd19 ]

SLIDER-1233 Lost nodes should not contribute to container failures (fix a fun-test)


> Lost nodes should not contribute to container failures
> ------------------------------------------------------
>
>                 Key: SLIDER-1233
>                 URL: https://issues.apache.org/jira/browse/SLIDER-1233
>             Project: Slider
>          Issue Type: Bug
>          Components: core
>            Reporter: Billie Rinaldi
>            Assignee: Billie Rinaldi
>             Fix For: Slider 1.0.0
>
>         Attachments: SLIDER-1233.001.patch, SLIDER-1233.002.patch
>
>
> If a container completes due to an NM being lost, we should not count this towards container failures that may eventually cause the AM to fail the application. We are already using a ContainerOutcome of Completed (rather than Failed) for this type of container exit, so we just need to change the failure counting in that case. Other failure types associated with Completed are killed by the AM, killed by the RM, and killed after app completion, none of which need to contribute to container failures.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)