hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jiraposter@reviews.apache.org (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3341) Enhance logging of initalized queue limit values
Date Wed, 09 Nov 2011 22:15:52 GMT

    [ 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

        

Mime
View raw message