[
https://issues.apache.org/jira/browse/YARN-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14528437#comment-14528437
]
Jason Lowe commented on YARN-3576:
----------------------------------
bq. In the NM log it is found that AM kills some of the containers
If it appears the AM is killing the containers, have you looked in the AM log
to see why it is choosing to do so?
bq. if the container is getting killed , why is its log present in container
logs?
Logs can be present for containers regardless of their exit status. It is
perfectly normal and expected that a container can have logs if the container
was killed after it was launched.
> In Log - Container getting killed by AM even when work preserving is enabled
> -----------------------------------------------------------------------------
>
> Key: YARN-3576
> URL: https://issues.apache.org/jira/browse/YARN-3576
> Project: Hadoop YARN
> Issue Type: Bug
> Environment: SUSE11 SP3
> 3 nodes cluster
> Reporter: Anushri
> Priority: Minor
>
> RM in HA mode
> NM running on one node
> work preserving enabled
> RM in HA mode one NM running work preserving is enabled An application is
> submitted and RM switch over happens. In the NM log it is found that AM kills
> some of the containers and those containers have exit code as 143. but in the
> container logs , logs are found for the same container.
> Problem :
> if work preserving is enabled why is it killing and cleaning the container?
> and if the container is getting killed , why is its log present in container
> logs?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
