[
https://issues.apache.org/jira/browse/YARN-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13914042#comment-13914042
]
Vinod Kumar Vavilapalli commented on YARN-1599:
-----------------------------------------------
I actually argue the contrary. We still have many cases where we don't have
tracking URLs for whatever reasons. So, I proposed a solution quite opposite to
what is being put up here - to always force the users to land on the RM page -
see YARN-1140. It is more clicks as argued here, but at the least we can then
be consistent. Similarly see YARN-1106.
I can't find the JIRA but given bulk of YARN-321 is done, we are changing the
RM UI to add much more information than is present. Clearly the per-framework
UI > RM UI in terms of data richness but the second UI isn't trivial anymore.
bq. 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
Why don't we fix this issue if that is the driving force. I don't expect a 404
if users go through the proxy (which they should!). Can you throw more light on
when this can happen?
> 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.1.5#6160)
