[
https://issues.apache.org/jira/browse/YARN-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13912383#comment-13912383
]
Zhijie Shen commented on YARN-1700:
-----------------------------------
Log url is nullable. In this scenario, the container is not launched. It is
also possible that the the container is completed, but the finish information
is not written into the history store. The correct fix should be correcting
AppAttemptBlock and ContainerBlock to handle the case that log url is null.
This is what YARN-1685 is supposed to do.
On the other side, even an container is not launched, we still want to record
it, though the current information we have collected can not tell whether the
container is finished after running some executable, or it is even not started.
However, we're going to improve the exposed information to let users see this
difference. Moreover, we are seeking for providing integrated access of the
information for both running and finished containers, via both RPC and web
interfaces. Given this done, users will monitor the containers before being
launched, being running, being completed and etc.
[~jira.shegalov], if you're fine with it. We can close the ticket as duplicate
of YARN-1685. Thanks!
> AHS records non-launched containers
> -----------------------------------
>
> Key: YARN-1700
> URL: https://issues.apache.org/jira/browse/YARN-1700
> Project: Hadoop YARN
> Issue Type: Sub-task
> Affects Versions: 2.4.0
> Reporter: Gera Shegalov
> Assignee: Gera Shegalov
> Attachments: YARN-1700.v01.patch, YARN-1700.v02.patch
>
>
> When testing AHS with a MR sleep job, AHS sometimes threw NPE out of
> AppAttemptBlock.render because logUrl in container report was null. I
> realized that this is because AHS may record containers that never launch.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
