[
https://issues.apache.org/jira/browse/YARN-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14164550#comment-14164550
]
Carlo Curino commented on YARN-2664:
------------------------------------
This is an "idea" of possible improvement of the GUI. The patch provides 2 new
sets information:
1) basic: each application listing shows the "reservation ID" if one exists
under which the job is run
2) advanced: there is a new "PlannerPage" page that shows a plot of the current
state of the plan.
I am NOT a UI guy, therefore the PlannerPage is very buggy, doesn't scale, and
use primitive javascripts
embedding and CSV formats.
Some areas of much needed improvement:
1) scale to a large number of jobs, and long time horizons
2) ACLs, maybe we should "gray out" all jobs that belong to other tenants
3) choose a better javascript library and data format (ideally getting data
through AJAX + REST?)
More ambitiously:
3) we would probably like to be able to zoom in/out, filter by user, filter by
size, alternate log/linear plot modes, etc...
4) Ideally we would like to also show also the "used" resources over time
"within" a reservation
(helps the user understand whether they over-provisioned their ask). This
means showing
a little bit of "past", and adding some tracking of usage (feedback loop
from scheduler to
plan needed for this).
So this patch is meant as a "seed" of an idea at the moment. If anyone with UI
competence is interested in
looking at this, I am happy to provide pointers/support from the YARN-1051
side.
> Improve RM webapp to expose info about reservations.
> ----------------------------------------------------
>
> Key: YARN-2664
> URL: https://issues.apache.org/jira/browse/YARN-2664
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Carlo Curino
> Attachments: YARN-2664.patch
>
>
> YARN-1051 provides a new functionality in the RM to ask for reservation on
> resources. Exposing this through the webapp GUI is important.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
