Sunil G commented on YARN-3603:

Hi [~jeffzhang]
Thank you for sharing the thoughts. I could remember an old JIRA YARN-1809, 
where UI is made similar for RM and HistoryServer.
Here we use {{getContainers)), where History/Timeline fills containers info 
from ApplicationContext (has all container info). But RM was taking from 
RMContext where only live containers are taken. I understood the need of killed 
containers here. it can help in debugging. However we have to segregate 
killed/preempted containers from completed containers. 

Hi [~leftnoteasy]
I also feel that we can have the information about killed/preempted container 
along with running containers in app attempt UI. In YARN-1809, we added for 
only running containers. Could you pls share your thoughts here.

> Application Attempts page confusing
> -----------------------------------
>                 Key: YARN-3603
>                 URL: https://issues.apache.org/jira/browse/YARN-3603
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: webapp
>    Affects Versions: 2.8.0
>            Reporter: Thomas Graves
>            Assignee: Sunil G
>         Attachments: 0001-YARN-3603.patch, 0002-YARN-3603.patch, 
> 0003-YARN-3603.patch, ahs1.png
> The application attempts page 
> (http://RM:8088/cluster/appattempt/appattempt_1431101480046_0003_000001)
> is a bit confusing on what is going on.  I think the table of containers 
> there is for only Running containers and when the app is completed or killed 
> its empty.  The table should have a label on it stating so.  
> Also the "AM Container" field is a link when running but not when its killed. 
>  That might be confusing.
> There is no link to the logs in this page but there is in the app attempt 
> table when looking at http://
> rm:8088/cluster/app/application_1431101480046_0003

This message was sent by Atlassian JIRA

Reply via email to