[
https://issues.apache.org/jira/browse/YARN-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012408#comment-16012408
]
Junping Du commented on YARN-6570:
----------------------------------
Just check trunk branch code and found that YARN-4597 (commit to 2.9 and trunk)
already included a fix by introducing SCHEDULED state for containers before
into running state. However, there is still a small issue that NEW state are
captured as SCHEDULED which doesn't seems to be right.
Put up a poc patch with quick fix. Patch with UT will come after.
> No logs were found for running application, running container
> -------------------------------------------------------------
>
> Key: YARN-6570
> URL: https://issues.apache.org/jira/browse/YARN-6570
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn
> Reporter: Sumana Sathish
> Assignee: Junping Du
> Priority: Critical
>
> 1.Obtain running containers from the following CLI for running application:
> yarn container -list appattempt
> 2. Couldnot fetch logs
> {code}
> Can not find any log file matching the pattern: ALL for the container
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
