hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3341) Enhance logging of initalized queue limit values
Date Mon, 14 Nov 2011 23:11:51 GMT

    [ 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

        

Mime
View raw message