hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yesha Vora (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-7175) Log collection fails when a container is acquired but not launched on NM
Date Fri, 08 Sep 2017 01:13:00 GMT

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

Yesha Vora updated YARN-7175:
-----------------------------
    Attachment: SparkApp.log

> Log collection fails when a container is acquired but not launched on NM
> ------------------------------------------------------------------------
>
>                 Key: YARN-7175
>                 URL: https://issues.apache.org/jira/browse/YARN-7175
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn
>            Reporter: Yesha Vora
>         Attachments: SparkApp.log
>
>
> Scenario:
> * Run Spark App
> * As soon as spark application finishes, Run "yarn application -status <appID>"
cli in a loop for 2-3 mins to check Log_aggreagtion status. 
> I'm noticing that log_aggregation status remains in "RUNNING" and eventually ends up
with "TIMED_OUT" status.  
> This situation happens when an application has acquired a container but it is not launched
on NM. 
> This scenario should be better handled and should not cause this delay to get the application
log. 



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

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


Mime
View raw message