[
https://issues.apache.org/jira/browse/YARN-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757788#comment-13757788
]
Thomas Graves commented on YARN-1140:
-------------------------------------
I understand always linking to the per app page to try to make it more
consistent but at the same time I don't like that power users will have to
click one more time. I also don't see how this solves the issue with the
tracking url being a bad link, unless you are also proposing to handle that
better on the app page? if an app finishes and doesn't set the history link
(for instance a non-mapreduce app) or crashes before they can set it, the
tracking url link is still going to to go a bad page.
> Tracking URL is broken in a lots of corner cases, and can be the AM page or
> the application page depending on the situation
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: YARN-1140
> URL: https://issues.apache.org/jira/browse/YARN-1140
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Vinod Kumar Vavilapalli
>
> Today, there are so many corner cases, specifically when the AM fails to
> start, when users will see that the tracking URL is broken or redirected to
> the per-app page. I am thinking of removing the tracking URL completely from
> the landing web-page and always force users to first jump on to the
> application-page. That way, there is consistency and there will always be one
> page that users can go to for their app information and then subsequently
> navigate to the AM page if all went well.
> Thoughts?
--
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
