[
https://issues.apache.org/jira/browse/YARN-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13951556#comment-13951556
]
Jian He commented on YARN-1885:
-------------------------------
Talked with Vinod offline, one thing we observed is that after RM restart, if
the new AM is not scheduled any containers on the nodes on which its previous
AM's containers were running, this NM won't get the application_completed
signal from RM when the new AM completes and so this NM won't aggregate the
logs for the previous containers of this application. But it should only be a
leak of local container logs. yarn logs -applicationId shouldn't return
nothing. it should at least return the latest AM's logs
> yarn logs command does not provide the application logs for some applications
> -----------------------------------------------------------------------------
>
> Key: YARN-1885
> URL: https://issues.apache.org/jira/browse/YARN-1885
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: Arpit Gupta
>
> During our HA testing we have seen cases where yarn application logs are not
> available through the cli but i can look at AM logs through the UI. RM was
> also being restarted in the background as the application was running.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
