[
https://issues.apache.org/jira/browse/MAPREDUCE-3897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222331#comment-13222331
]
Hudson commented on MAPREDUCE-3897:
-----------------------------------
Integrated in Hadoop-Mapreduce-0.23-Build #216 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Build/216/])
Merge -c 1296898 from trunk to branch-0.23 to fix MAPREDUCE-3897. Fixed
computation of maxActiveAppsPerUser for queues by using capacity and not
max-capacity since we are already scaling it by userLimitFactor. (Revision
1296899)
Result = FAILURE
acmurthy :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1296899
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
*
/hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestApplicationLimits.java
> capacity scheduler - maxActiveApplicationsPerUser calculation can be wrong
> --------------------------------------------------------------------------
>
> Key: MAPREDUCE-3897
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3897
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Thomas Graves
> Assignee: Eric Payne
> Priority: Critical
> Fix For: 0.23.2
>
> Attachments: MAPREDUCE-3897-1.txt, MAPREDUCE-3897-1.txt,
> MAPREDUCE-3897-2.txt
>
>
> The capacity scheduler calculates the maxActiveApplications and the
> maxActiveApplicationsPerUser based on the config
> yarn.scheduler.capacity.maximum-applications or default 10000.
> MaxActiveApplications = max ( ceil ( clusterMemory/minAllocation *
> maxAMResource% * absoluteMaxCapacity), 1)
> MaxActiveAppsPerUser = max( ceil (maxActiveApplicationsComputedAbove *
> (userLimit%/100) * userLimitFactor), 1)
> maxActiveApplications is already multiplied by the queue absolute MAXIMUM
> capacity, so if max capacity > capacity and if you have user limit factor 1
> (which is the default) and only 1 user is running, that user will not be
> allowed to use over the queue capacity, so having it relative to MAX capacity
> doesn't make sense. That user could easily end up in a deadlock and all its
> space used by application masters.
--
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
