RM web UI scheduler link not as useful as should be

Details

Description

The resource manager web ui page for scheduler doesn't have all the information about the configuration like the jobtracker page used to have. The things it seems to show you are the current queues - each queues used, set, and max percent and then what apps are running in that queue.

It doesn't list any of yarn.scheduler.capacity.maximum-applications, yarn.scheduler.capacity.maximum-am-resource-percent, yarn.scheduler.capacity.<queue-path>.user-limit-factor, yarn.scheduler.capacity.<queue-path>.minimum-user-limit-percent, queue state, active users and percent used by user

Anupam Seth
added a comment - 07/Nov/11 21:06 Thanks Jon!
Not sure if I am missing / misunderstanding something, but upon reading the discussion, it seems that MAPREDUCE-1118 applies only to 0.20 and 0.22 and not 0.23 / mrv2.

By default the dropdown text box for each leaf queue is hidden so it doesn't clutter the initial rendering of the page.

In addition the application filtering is improved but not totally fixed. Clicking on a leaf queue now properly filters for the specific queue (no more accidental substring matching on other queues), but filtering on a parent queue is still broken. Fixing the filtering for the parent queues is a bit more involved and should be handled by another JIRA.

Jason Lowe
added a comment - 04/Jan/12 20:56 Patch provides a dropdown textbox for each capacity scheduler leaf queue showing:
Queue State
Capacity
Max Capacity
Used Capacity
Absolute Capacity
Absolute Max Capacity
Utilization
Used Resources
Num Active Applications
Num Pending Applications
Num Containers
Max Applications
Max Applications Per User
Max Active Applications
Max Active Applications Per User
User Limit
User Limit Factor
By default the dropdown text box for each leaf queue is hidden so it doesn't clutter the initial rendering of the page.
In addition the application filtering is improved but not totally fixed. Clicking on a leaf queue now properly filters for the specific queue (no more accidental substring matching on other queues), but filtering on a parent queue is still broken. Fixing the filtering for the parent queues is a bit more involved and should be handled by another JIRA.

Hadoop QA
added a comment - 04/Jan/12 22:14 +1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12509455/MAPREDUCE-3326.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed unit tests in .
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1539//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1539//console
This message is automatically generated.

Sorry I forgot to mention that the patch is implemented in terms of the web dao objects, so the web services have access to the same information as the web page. The web services tests were updated as part of the patch to verify this. I was going to update the web services documentation, but Tom informed me that part hasn't been written yet. Tom said he'd update the docs to describe the new fields in the web dao objects before the first draft is submitted. If those docs go in before this patch then I can update the patch, or we can file a JIRA to track updating the docs.

Jason Lowe
added a comment - 05/Jan/12 19:23 Sorry I forgot to mention that the patch is implemented in terms of the web dao objects, so the web services have access to the same information as the web page. The web services tests were updated as part of the patch to verify this. I was going to update the web services documentation, but Tom informed me that part hasn't been written yet. Tom said he'd update the docs to describe the new fields in the web dao objects before the first draft is submitted. If those docs go in before this patch then I can update the patch, or we can file a JIRA to track updating the docs.

One nit - an existing bug is that the display of the queue's used capacity at runtime is broken because it display's 'used' relative to the queue's capacity and not the parent's capacity as shown in the above attachment.

I think the display should be relative to parent's capacity and not leaf queues as everything else in the display is relative to parent's capacity.

Jason, if you don't mind can we fix that alongwith this patch? Thanks!

Arun C Murthy
added a comment - 05/Jan/12 19:25 One nit - an existing bug is that the display of the queue's used capacity at runtime is broken because it display's 'used' relative to the queue's capacity and not the parent's capacity as shown in the above attachment.
I think the display should be relative to parent's capacity and not leaf queues as everything else in the display is relative to parent's capacity.
Jason, if you don't mind can we fix that alongwith this patch? Thanks!

-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.

Hadoop QA
added a comment - 05/Jan/12 19:34 -1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12509595/Screen+shot+2012-01-05+at+11.23.26+AM.png
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
-1 patch. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1549//console
This message is automatically generated.