[
https://issues.apache.org/jira/browse/YARN-4848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15325164#comment-15325164
]
Varun Saxena commented on YARN-4848:
------------------------------------
Looked at this.
Now what we have currently in node pages is a list of apps and containers
running on that node(IMO should be there). Please note that NMs' will have
state and diagnostics of apps and containers as well which might be useful (say
if localization failed or container launch failed).
Flow for current NM pages is as under :
1. From list of running apps, we click on each app and go to individual app
page(NM view of app). Now the only thing we see there is user, app state and a
list of containers belonging to this app(running on that NM). We can click on
each one of these containers and go to an individual container page.
2. From the list of containers too, we can click on each one and go to
individual container page. This page gives us container state, exit code,
diagnostics, resources required by the container and link to logs.
Now for 1, I think instead of going to NM view of app we can directly go to
Main app page(as proposed). The only downside of this is that we will then have
to go to app attempt page to see containers instead of directly seeing
containers running. And also we wont be directly able to see containers of this
app running on a particular node.
But I do not think this is required as users will try to find out details about
only containers which are stuck or failing, instead of trying to find out which
containers are running on which node.
For 2, however we do not have a single container page(RM view of container). We
see all containers in a timeline view on app attempt page. And we see a small
table for container on the side.
Making user jump by clicking container link on NM page to app attempt page will
be awkward.
I think what we can do is that have a separate Container page which has details
from both NM and RM for a container. The table next to Container timeline view
can have bare minimum information.
With ATSv2 we will have container metrics (CPU / Memory) available to us as
well (even as a time series). Maybe in that individual container page we can
fetch these metrics as a time series and plot a line graph or some other type
of graph.
> [YARN-3368] Unify app/container pages and other miscellaneous issues
> --------------------------------------------------------------------
>
> Key: YARN-4848
> URL: https://issues.apache.org/jira/browse/YARN-4848
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: webapp
> Reporter: Varun Saxena
> Assignee: Varun Saxena
>
> We need to consolidate app and container views. Currently apps and container
> views from NM page do not land up on a unified app/container page.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
