hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gera Shegalov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1599) webUI rm.webapp.AppBlock should redirect to a history App page if and when available
Date Thu, 27 Feb 2014 10:00:25 GMT

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

Gera Shegalov commented on YARN-1599:

[~vinodkv], with v03 we are no longer forcing the redirect. I agree with this point, raised
by [~jlowe] as well. You can still access the RM app via the corresponding link, as you can
see from the screenshot. I simply moved the tracking UI link that our users really want to
see to the 1st column. And now users tend to click it first. 

bq. 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?

However, you are correct that 404 on the link from RM app to AM logs should be fixed as well.
404 is caused by the log aggregation after the local logs are deleted.

> 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

This message was sent by Atlassian JIRA

View raw message