Matteo Mazzucchelli commented on YARN-2664:

Thank for your feedback
high level comments/questions
a) This is a view of reservations and does not indicate actual allocations 
right? But the legend for y axis says Utilization GB. Allocation would be a 
great addition (knowing how much is left of my reservation etc)
Yes, the graph indicate the memory allocations for the reservations. For a 
better understanding I will change the label

b) This shows everything in terms of memory but not cpu, right? Should we add a 
switch to show both and in future other resource types? Showing them together 
is more correct but harder to visualize.
I can add a "switch" to change from the "memory view" to the "CPU view". As you 
said, I think it is very hard to put them together.

Minor usability issues
a) How is the time window for the slider and time window that is selected in 
the slider chosen? Some times it would keep the slider to some point before the 
current time at other times it would show future time as part of the view. Also 
if there was no reservations it would not go to current time until a new 
reservation shows up?
The window, by default, is set from the time of the first reservation starts to 
the time of the last reservation ends. I will check a little more the slider. 
Do you think it's better that the slider starts from the current time?

b) related to previous, why does refresh button on page allow me to move the 
chosen time window forward but not the refresh button. Maybe rename the refresh 
to refresh queues? 
The refresh button on the page reloads the data and the graph. The refresh 
button of the browser reload the entire page. As you suggest the renaming of 
the button is a good point.

Also provide a refresh time button if c) below cannot be solved?
c) is there a query parameter or some other way to get back to a specific 
queue? That would help not having to do drop down every time i refresh the page
At this moment you cant do that. The page was designed to work with 
asynchronous calls to retrieve only the data and to reload the graph.

As soon as possible I will submit the new patch

> 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
>            Assignee: Matteo Mazzucchelli
>         Attachments: PlannerPage_screenshot.pdf, YARN-2664.1.patch, 
> YARN-2664.2.patch, YARN-2664.3.patch, YARN-2664.4.patch, YARN-2664.5.patch, 
> YARN-2664.6.patch, YARN-2664.7.patch, YARN-2664.patch, legal.patch, 
> screenshot_reservation_UI.pdf
> 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

Reply via email to