hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (YARN-6570) No logs were found for running application, running container
Date Tue, 26 Sep 2017 15:38:00 GMT

     [ https://issues.apache.org/jira/browse/YARN-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jason Lowe reopened YARN-6570:

I missed the NEW state exposure in the trunk/branch-2 patch which will also be problematic.
 This not only has to be addressed in RMNodeImpl but also other places where the code assumes
!= RUNNING is the same as == COMPLETED.  NMClient#stopContainer does this, and there may also
be changes needed elsewhere (e.g.: RMContainerImpl.ContainerRecoveredTransition).

Reverting the patch from trunk and branch-2 until this is sorted out.

> 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
>             Fix For: 2.9.0, 3.0.0-beta1, 3.1.0
>         Attachments: YARN-6570-branch-2.8.001.patch, YARN-6570-branch-2.8.002.patch,
YARN-6570.poc.patch, YARN-6570-v2.patch, YARN-6570-v3.patch
> 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

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message