[
https://issues.apache.org/jira/browse/YARN-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13935742#comment-13935742
]
Gera Shegalov commented on YARN-1599:
-------------------------------------
[~jlowe] thanks for pointing in the right direction. E.g., setting
yarn.log.server.url to
{code}http://${mapreduce.jobhistory.webapp.address}/jobhistory/logs{code}
solves the problem on the pseudo-distributed cluster.
> webUI rm.webapp.AppBlock should redirect to a history App page if and when
> available
> ------------------------------------------------------------------------------------
>
> Key: YARN-1599
> URL: https://issues.apache.org/jira/browse/YARN-1599
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.0.5-alpha, 2.2.0
> Reporter: Gera Shegalov
> Assignee: Gera Shegalov
> Attachments: Screen Shot 2014-01-16 at 6.52.17 PM.png, Screen Shot
> 2014-01-16 at 7.30.32 PM.png, YARN-1599.v01.patch, YARN-1599.v02.patch,
> YARN-1599.v03.patch
>
>
> When the log aggregation is enabled, and the application finishes, our users
> think that the AppMaster logs were lost because the link to the AM attempt
> logs are not updated and result in HTTP 404. Only tracking URL is updated. In
> order to have a smoother user experience, we propose to simply redirect to
> the new tracking URL when the page with invalid log links is accessed.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
