[ https://issues.apache.org/jira/browse/YARN-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484134#comment-13484134 ]
Hudson commented on YARN-180: ----------------------------- Integrated in Hadoop-Mapreduce-trunk #1236 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1236/]) YARN-180. Capacity scheduler - containers that get reserved create container token to early (acmurthy and bobby) (Revision 1401703) Result = FAILURE bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1401703 Files : * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/LeafQueue.java > Capacity scheduler - containers that get reserved create container token to > early > --------------------------------------------------------------------------------- > > Key: YARN-180 > URL: https://issues.apache.org/jira/browse/YARN-180 > Project: Hadoop YARN > Issue Type: Bug > Components: capacityscheduler > Affects Versions: 0.23.3 > Reporter: Thomas Graves > Assignee: Arun C Murthy > Priority: Critical > Fix For: 3.0.0, 2.0.3-alpha, 0.23.5 > > Attachments: YARN-180-branch_0.23.patch, YARN-180.patch, > YARN-180.patch, YARN-180.patch > > > The capacity scheduler has the ability to 'reserve' containers. > Unfortunately before it decides that it goes to reserved rather then > assigned, the Container object is created which creates a container token > that expires in roughly 10 minutes by default. > This means that by the time the NM frees up enough space on that node for the > container to move to assigned the container token may have expired. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira