You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Rohith (JIRA)" <ji...@apache.org> on 2014/03/03 14:53:24 UTC

[jira] [Commented] (YARN-1206) Container logs link is broken on RM web UI after application finished

    [ https://issues.apache.org/jira/browse/YARN-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13918064#comment-13918064 ] 

Rohith commented on YARN-1206:
------------------------------

 I am able to reproduce this issue in today's trunk with log aggregation disable. I verified hadoop-2.1 , this issue does not ocure.

I just going through fix for YARN-649, found there is null check for container in ContainerLogsUtils.getContainerLogDirs() method.
{noformat}
   if (container == null) {
      throw new YarnException("Container does not exist.");
    }
{noformat}
In hadoop-2.1, above piece of code not there. I am not pretty sure why this is added.!!

Basically if container is COMPLETED  than it will be  removed from NMContext ( NodeStatusUpdaterImpl.updateAndGetContainerStatuses() ). NM does not have any information regarding this container. 

Is it really required to have this check ? 

> Container logs link is broken on RM web UI after application finished
> ---------------------------------------------------------------------
>
>                 Key: YARN-1206
>                 URL: https://issues.apache.org/jira/browse/YARN-1206
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Jian He
>            Priority: Blocker
>
> With log aggregation disabled, when container is running, its logs link works properly, but after the application is finished, the link shows 'Container does not exist.'



--
This message was sent by Atlassian JIRA
(v6.2#6252)