hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohith (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1206) Container logs link is broken on RM web UI after application finished
Date Mon, 17 Mar 2014 04:14:45 GMT

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

Rohith commented on YARN-1206:

Hi Jian, 
   Thank  you for looking into patch.

There are 2 scenarios.
1. When Container is Running, NM maintains all running container from NMContext. Accessing
container logs link is validated by getting container from NMContext(container == null ) which
works fine.

2. When Container is Completed, NM removes completed container from NMContext(NodeStatusUpdaterImpl.removeCompletedContainersFromContext()).
 After application is finished, accessing container logs link tying to validate containerId
from NMContext which is already removed in heartbeat.

When log aggregation is disabled, request for container log view forwarded to NM. But NM does
not have completed container list. So, for already finished containers, we need not to check
for null.

> 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
>            Assignee: Rohith
>            Priority: Blocker
>         Attachments: YARN-1206.patch
> 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

View raw message