[
https://issues.apache.org/jira/browse/MAPREDUCE-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145653#comment-13145653
]
Hadoop QA commented on MAPREDUCE-3341:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12502769/MAPREDUCE-3341-branch_0_23.patch
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 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 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/1256//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1256//console
This message is automatically generated.
> Enhance logging of initalized queue limit values
> ------------------------------------------------
>
> Key: MAPREDUCE-3341
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3341
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Anupam Seth
> Assignee: Anupam Seth
> Attachments: MAPREDUCE-3341-branch_0_23.patch
>
>
> Currently the RM log shows only a partial set of the limits that are
> configured when a queue is initialized / reinitialized.
> For example, this is what is currently shown in the RM log for an initialized
> queue:
> # <datestamp> INFO
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue:
> Initializing
> default, capacity=0.25, asboluteCapacity=0.25, maxCapacity=25.0,
> asboluteMaxCapacity=0.25, userLimit=100,
> userLimitFactor=20.0, maxApplications=2500, maxApplicationsPerUser=50000,
> state=RUNNING,
> acls=ADMINISTER_QUEUE:*SUBMIT_JOB:*ADMINISTER_JOBS:*
> Breaking down the line above, shows:
> capacity=0.25
> asboluteCapacity=0.25
> maxCapacity=25.0
> asboluteMaxCapacity=0.25
> userLimit=100
> userLimitFactor=20.0
> maxApplications=2500
> maxApplicationsPerUser=50000
> It might be nice if we could include more information such as
> maxActiveApplications, maxActiveApplicationsPerUser, utilization, and
> usedCapacity along with information on how each of these is computed (i.e.
> formulae used) (Thanks to Phil Su for requesting this).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
