You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Anupam Seth (Created) (JIRA)" <ji...@apache.org> on 2011/11/03 16:49:32 UTC
[jira] [Created] (MAPREDUCE-3341) Enhance logging of initalized
queue limit values
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
Reporter: Anupam Seth
Assignee: Anupam Seth
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
[jira] [Commented] (MAPREDUCE-3341) Enhance logging of initalized
queue limit values
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150025#comment-13150025 ]
Hudson commented on MAPREDUCE-3341:
-----------------------------------
Integrated in Hadoop-Hdfs-trunk-Commit #1344 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/1344/])
MAPREDUCE-3341. Enhance logging of initalized queue limit values. (Anupam Seth via mahadev)
mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1201947
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/LeafQueue.java
> 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
> Fix For: 0.23.1
>
> Attachments: MAPREDUCE-3341-branch_0_23.patch, 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
[jira] [Commented] (MAPREDUCE-3341) Enhance logging of initalized
queue limit values
Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147351#comment-13147351 ]
Hadoop QA commented on MAPREDUCE-3341:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12503139/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/1287//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1287//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, 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
[jira] [Commented] (MAPREDUCE-3341) Enhance logging of initalized
queue limit values
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147266#comment-13147266 ]
jiraposter@reviews.apache.org commented on MAPREDUCE-3341:
----------------------------------------------------------
bq. On 2011-11-08 17:27:47, Robert Evans wrote:
bq. > Mostly looks good, just one minor nit.
Thanks Bobby for noticing that! Below is an example log output. I will upload a new patch removing the unnecssary whitespace.
2011-11-09 20:20:19,309 INFO capacity.LeafQueue (LeafQueue.java:setupQueueConfigs(250)) - Initializing default
capacity = 0.4[ = (float) configuredCapacity / 100 ]
asboluteCapacity = 0.4[ = parentAbsoluteCapacity * capacity ]
maxCapacity = -0.01[ = configuredMaxCapacity ]
absoluteMaxCapacity = 3.4028235E38[ = Float.MAX_VALUE if maximumCapacity undefined, = (parentAbsoluteCapacity * maximumCapacity) / 100 otherwise ]
userLimit = 100[ = configuredUserLimit ]
userLimitFactor = 1.0[ = configuredUserLimitFactor ]
maxApplications = 4000[ = (int)(configuredMaximumSystemApplications * absoluteCapacity) ]
maxApplicationsPerUser = 4000[ = (int)(maxApplications * (userLimit / 100.0f) * userLimitFactor) ]
maxActiveApplications = 1[ = max( (int)((clusterResourceMemory / (float)DEFAULT_AM_RESOURCE) * maxAMResourcePercent * absoluteCapacity), 1) ]
maxActiveApplicationsPerUser = 1[ = (int)(maxActiveApplications * (userLimit / 100.0f) * userLimitFactor) ]
utilization = 0.0[ = usedResourcesMemory / queueLimit ]
usedCapacity = 0.0[ = usedResourcesMemory / (clusterResourceMemory * capacity) ]
maxAMResourcePercent = 0.1[ = configuredMaximumAMResourcePercent ]
minimumAllocationFactor = 0.9[ = (float)(maximumAllocationMemory - minimumAllocationMemory) / maximumAllocationMemory ]
numContainers = 0[ = currentNumContainers ]
state = RUNNING[ = configuredState ]
acls = ADMINISTER_QUEUE:*SUBMIT_APPLICATIONS:*[ = configuredAcls ]
- Anupam
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2775/#review3112
-----------------------------------------------------------
On 2011-11-09 20:34:10, Anupam Seth wrote:
bq.
bq. -----------------------------------------------------------
bq. This is an automatically generated e-mail. To reply, visit:
bq. https://reviews.apache.org/r/2775/
bq. -----------------------------------------------------------
bq.
bq. (Updated 2011-11-09 20:34:10)
bq.
bq.
bq. Review request for Robert Evans and Jonathan Eagles.
bq.
bq.
bq. Summary
bq. -------
bq.
bq. Enhance logging for queues in capacity scheduler
bq.
bq.
bq. This addresses bug MAPREDUCE-3341.
bq. https://issues.apache.org/jira/browse/MAPREDUCE-3341
bq.
bq.
bq. Diffs
bq. -----
bq.
bq. branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/LeafQueue.java 1198816
bq.
bq. Diff: https://reviews.apache.org/r/2775/diff
bq.
bq.
bq. Testing
bq. -------
bq.
bq.
bq. Thanks,
bq.
bq. Anupam
bq.
bq.
> 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
[jira] [Commented] (MAPREDUCE-3341) Enhance logging of initalized
queue limit values
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150466#comment-13150466 ]
Hudson commented on MAPREDUCE-3341:
-----------------------------------
Integrated in Hadoop-Mapreduce-0.23-Build #94 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Build/94/])
MAPREDUCE-3341. Enhance logging of initalized queue limit values. (Anupam Seth via mahadev) - Merging r1201947 from trunk
mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1201949
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/LeafQueue.java
> 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
> Fix For: 0.23.1
>
> Attachments: MAPREDUCE-3341-branch_0_23.patch, 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
[jira] [Updated] (MAPREDUCE-3341) Enhance logging of initalized
queue limit values
Posted by "Anupam Seth (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anupam Seth updated MAPREDUCE-3341:
-----------------------------------
Affects Version/s: 0.23.0
Status: Patch Available (was: Open)
> 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
[jira] [Commented] (MAPREDUCE-3341) Enhance logging of initalized
queue limit values
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150027#comment-13150027 ]
Hudson commented on MAPREDUCE-3341:
-----------------------------------
Integrated in Hadoop-Common-trunk-Commit #1270 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/1270/])
MAPREDUCE-3341. Enhance logging of initalized queue limit values. (Anupam Seth via mahadev)
mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1201947
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/LeafQueue.java
> 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
> Fix For: 0.23.1
>
> Attachments: MAPREDUCE-3341-branch_0_23.patch, 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
[jira] [Commented] (MAPREDUCE-3341) Enhance logging of initalized
queue limit values
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150037#comment-13150037 ]
Hudson commented on MAPREDUCE-3341:
-----------------------------------
Integrated in Hadoop-Hdfs-0.23-Commit #169 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Commit/169/])
MAPREDUCE-3341. Enhance logging of initalized queue limit values. (Anupam Seth via mahadev) - Merging r1201947 from trunk
mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1201949
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/LeafQueue.java
> 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
> Fix For: 0.23.1
>
> Attachments: MAPREDUCE-3341-branch_0_23.patch, 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
[jira] [Commented] (MAPREDUCE-3341) Enhance logging of initalized
queue limit values
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147333#comment-13147333 ]
jiraposter@reviews.apache.org commented on MAPREDUCE-3341:
----------------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2775/
-----------------------------------------------------------
(Updated 2011-11-09 22:14:25.939590)
Review request for Robert Evans and Jonathan Eagles.
Changes
-------
Uploading new diff
Summary
-------
Enhance logging for queues in capacity scheduler
This addresses bug MAPREDUCE-3341.
https://issues.apache.org/jira/browse/MAPREDUCE-3341
Diffs (updated)
-----
branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/LeafQueue.java 1199955
Diff: https://reviews.apache.org/r/2775/diff
Testing
-------
Thanks,
Anupam
> 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, 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
[jira] [Commented] (MAPREDUCE-3341) Enhance logging of initalized
queue limit values
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147813#comment-13147813 ]
jiraposter@reviews.apache.org commented on MAPREDUCE-3341:
----------------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2775/#review3157
-----------------------------------------------------------
Ship it!
looks good to me +1 (non-binding)
- Robert
On 2011-11-09 22:14:25, Anupam Seth wrote:
bq.
bq. -----------------------------------------------------------
bq. This is an automatically generated e-mail. To reply, visit:
bq. https://reviews.apache.org/r/2775/
bq. -----------------------------------------------------------
bq.
bq. (Updated 2011-11-09 22:14:25)
bq.
bq.
bq. Review request for Robert Evans and Jonathan Eagles.
bq.
bq.
bq. Summary
bq. -------
bq.
bq. Enhance logging for queues in capacity scheduler
bq.
bq.
bq. This addresses bug MAPREDUCE-3341.
bq. https://issues.apache.org/jira/browse/MAPREDUCE-3341
bq.
bq.
bq. Diffs
bq. -----
bq.
bq. branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/LeafQueue.java 1199955
bq.
bq. Diff: https://reviews.apache.org/r/2775/diff
bq.
bq.
bq. Testing
bq. -------
bq.
bq.
bq. Thanks,
bq.
bq. Anupam
bq.
bq.
> 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, 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
[jira] [Commented] (MAPREDUCE-3341) Enhance logging of initalized
queue limit values
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150438#comment-13150438 ]
Hudson commented on MAPREDUCE-3341:
-----------------------------------
Integrated in Hadoop-Hdfs-trunk #864 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/864/])
MAPREDUCE-3341. Enhance logging of initalized queue limit values. (Anupam Seth via mahadev)
mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1201947
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/LeafQueue.java
> 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
> Fix For: 0.23.1
>
> Attachments: MAPREDUCE-3341-branch_0_23.patch, 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
[jira] [Commented] (MAPREDUCE-3341) Enhance logging of initalized
queue limit values
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150447#comment-13150447 ]
Hudson commented on MAPREDUCE-3341:
-----------------------------------
Integrated in Hadoop-Hdfs-0.23-Build #77 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/77/])
MAPREDUCE-3341. Enhance logging of initalized queue limit values. (Anupam Seth via mahadev) - Merging r1201947 from trunk
mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1201949
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/LeafQueue.java
> 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
> Fix For: 0.23.1
>
> Attachments: MAPREDUCE-3341-branch_0_23.patch, 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
[jira] [Commented] (MAPREDUCE-3341) Enhance logging of initalized
queue limit values
Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (MAPREDUCE-3341) Enhance logging of initalized
queue limit values
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150479#comment-13150479 ]
Hudson commented on MAPREDUCE-3341:
-----------------------------------
Integrated in Hadoop-Mapreduce-trunk #898 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/898/])
MAPREDUCE-3341. Enhance logging of initalized queue limit values. (Anupam Seth via mahadev)
mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1201947
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/LeafQueue.java
> 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
> Fix For: 0.23.1
>
> Attachments: MAPREDUCE-3341-branch_0_23.patch, 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
[jira] [Commented] (MAPREDUCE-3341) Enhance logging of initalized
queue limit values
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150039#comment-13150039 ]
Hudson commented on MAPREDUCE-3341:
-----------------------------------
Integrated in Hadoop-Common-0.23-Commit #170 (See [https://builds.apache.org/job/Hadoop-Common-0.23-Commit/170/])
MAPREDUCE-3341. Enhance logging of initalized queue limit values. (Anupam Seth via mahadev) - Merging r1201947 from trunk
mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1201949
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/LeafQueue.java
> 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
> Fix For: 0.23.1
>
> Attachments: MAPREDUCE-3341-branch_0_23.patch, 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
[jira] [Commented] (MAPREDUCE-3341) Enhance logging of initalized
queue limit values
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150049#comment-13150049 ]
Hudson commented on MAPREDUCE-3341:
-----------------------------------
Integrated in Hadoop-Mapreduce-trunk-Commit #1292 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/1292/])
MAPREDUCE-3341. Enhance logging of initalized queue limit values. (Anupam Seth via mahadev)
mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1201947
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/LeafQueue.java
> 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
> Fix For: 0.23.1
>
> Attachments: MAPREDUCE-3341-branch_0_23.patch, 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
[jira] [Updated] (MAPREDUCE-3341) Enhance logging of initalized
queue limit values
Posted by "Mahadev konar (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mahadev konar updated MAPREDUCE-3341:
-------------------------------------
Resolution: Fixed
Fix Version/s: 0.23.1
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Just committed this. Thanks Anupam.
> 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
> Fix For: 0.23.1
>
> Attachments: MAPREDUCE-3341-branch_0_23.patch, 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
[jira] [Updated] (MAPREDUCE-3341) Enhance logging of initalized
queue limit values
Posted by "Anupam Seth (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anupam Seth updated MAPREDUCE-3341:
-----------------------------------
Attachment: MAPREDUCE-3341-branch_0_23.patch
> 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
> 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
[jira] [Commented] (MAPREDUCE-3341) Enhance logging of initalized
queue limit values
Posted by "Mahadev konar (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150017#comment-13150017 ]
Mahadev konar commented on MAPREDUCE-3341:
------------------------------------------
+1 looks good.
> 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, 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
[jira] [Commented] (MAPREDUCE-3341) Enhance logging of initalized
queue limit values
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147265#comment-13147265 ]
jiraposter@reviews.apache.org commented on MAPREDUCE-3341:
----------------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2775/
-----------------------------------------------------------
(Updated 2011-11-09 20:34:10.717792)
Review request for Robert Evans and Jonathan Eagles.
Changes
-------
Linking to JIRA
Summary
-------
Enhance logging for queues in capacity scheduler
This addresses bug MAPREDUCE-3341.
https://issues.apache.org/jira/browse/MAPREDUCE-3341
Diffs
-----
branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/LeafQueue.java 1198816
Diff: https://reviews.apache.org/r/2775/diff
Testing
-------
Thanks,
Anupam
> 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
[jira] [Updated] (MAPREDUCE-3341) Enhance logging of initalized
queue limit values
Posted by "Anupam Seth (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anupam Seth updated MAPREDUCE-3341:
-----------------------------------
Attachment: MAPREDUCE-3341-branch_0_23.patch
> 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, 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
[jira] [Commented] (MAPREDUCE-3341) Enhance logging of initalized
queue limit values
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150059#comment-13150059 ]
Hudson commented on MAPREDUCE-3341:
-----------------------------------
Integrated in Hadoop-Mapreduce-0.23-Commit #181 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Commit/181/])
MAPREDUCE-3341. Enhance logging of initalized queue limit values. (Anupam Seth via mahadev) - Merging r1201947 from trunk
mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1201949
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/LeafQueue.java
> 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
> Fix For: 0.23.1
>
> Attachments: MAPREDUCE-3341-branch_0_23.patch, 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