Thomas Graves commented on YARN-3600:

So the change does fix the broken link issue, but it seems to me other things 
are broken with this page.  Obviously if it ran for a while it got an AM and 
there fore should have a valid container.  But I guess that link only works if 
its actually running?

The container table below that also confused me a bit.  I thought at first it 
was list of AM containers, but after playing with it its really list of running 
containers.  I think we should add heading for that.  I filed separate jira for 
those things.

Anyway, +1.  Thanks!

> AM container link is broken (on a killed application, at least)
> ---------------------------------------------------------------
>                 Key: YARN-3600
>                 URL: https://issues.apache.org/jira/browse/YARN-3600
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.8.0
>            Reporter: Sergey Shelukhin
>            Assignee: Naganarasimha G R
>         Attachments: YARN-3600.20150508-1.patch
> Running some fairly recent (couple weeks ago) version of 2.8.0-SNAPSHOT. 
> I have an application that ran fine for a while and then I yarn kill-ed it. 
> Now when I go to the only app attempt URL (like so: http://(snip RM host 
> name):8088/cluster/appattempt/appattempt_1429683757595_0795_000001)
> I see:
> AM Container:         container_1429683757595_0795_01_000001
> Node:         N/A 
> and the container link goes to {noformat}http://(snip RM host 
> name):8088/cluster/N/A
> {noformat}
> which obviously doesn't work

This message was sent by Atlassian JIRA

Reply via email to