hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (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 14:11:21 GMT

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

Jason Lowe commented on YARN-1599:

I'd rather not change the meaning of the exisiting URLs.  If the user wants to see the app-specific
UI if there is one, that's the purpose of the proxy URL provided by the job client when the
job launches.  If the user wants to see the RM's details on the application then that's the
purpose of the RM app URL.

If the issue is users tend to click on the left link instead of the right link when they want
to go to the app-framework-specific UI for an app then I'd rather discuss swapping the links
in the application table rather than change what URLs go where by default.

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

I'm confused about the 404 scenario.  If log aggregation is configured and working properly,
the NM should redirect to the aggregated logs server when the logs are not present, and the
logs are not deleted until log aggregation completes.  The user would briefly see "Redirecting
to log server for container_xxx" during the redirect.  Is yarn.log.server.url configured properly?

> 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