[
https://issues.apache.org/jira/browse/YARN-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13769199#comment-13769199
]
Lohit Vijayarenu commented on YARN-1206:
----------------------------------------
We have seen case where upon enabling log aggregation, container link are
broken because logs are aggregated to HDFS. If link is not updated to point ot
history server, those will be broken links. Broken here is to say that
nodemangaer will not be able to display logs (since they are aggregated to hdfs)
One way to reproduce this is, run application to completion, then click
application link, something like
http://hadoop-rm-host:port/cluster/app/application_1379365648572_0001
Then click on 'logs' link next to ApplicationMaster attempt. This will point to
page on NM displaying the below message
"Failed while trying to construct the redirect url to the log server. Log
Server url may not be configured
Unknown container. Container either has not started or has already completed or
doesn't belong to this node at all."
> 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
> Labels: 2.1.1-beta
>
> When container is running, its logs link works properly, but after the
> application is finished, the link shows 'Container does not exist.'
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
