[jira] [Commented] (YARN-180) Capacity scheduler - containers that get reserved create container token to early
[ 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
[jira] [Commented] (YARN-180) Capacity scheduler - containers that get reserved create container token to early
[ https://issues.apache.org/jira/browse/YARN-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484093#comment-13484093 ] Hudson commented on YARN-180: - Integrated in Hadoop-Hdfs-trunk #1206 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1206/]) YARN-180. Capacity scheduler - containers that get reserved create container token to early (acmurthy and bobby) (Revision 1401703) Result = SUCCESS 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
[jira] [Commented] (YARN-180) Capacity scheduler - containers that get reserved create container token to early
[ https://issues.apache.org/jira/browse/YARN-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484076#comment-13484076 ] Hudson commented on YARN-180: - Integrated in Hadoop-Hdfs-0.23-Build #415 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/415/]) YARN-180. Capacity scheduler - containers that get reserved create container token to early (acmurthy and bobby) (Revision 1401706) Result = SUCCESS bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1401706 Files : * /hadoop/common/branches/branch-0.23/hadoop-yarn-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/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
[jira] [Commented] (YARN-180) Capacity scheduler - containers that get reserved create container token to early
[ https://issues.apache.org/jira/browse/YARN-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484034#comment-13484034 ] Hudson commented on YARN-180: - Integrated in Hadoop-Yarn-trunk #16 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/16/]) YARN-180. Capacity scheduler - containers that get reserved create container token to early (acmurthy and bobby) (Revision 1401703) Result = SUCCESS 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
[jira] [Commented] (YARN-180) Capacity scheduler - containers that get reserved create container token to early
[ https://issues.apache.org/jira/browse/YARN-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483270#comment-13483270 ] Hudson commented on YARN-180: - Integrated in Hadoop-trunk-Commit #2922 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/2922/]) YARN-180. Capacity scheduler - containers that get reserved create container token to early (acmurthy and bobby) (Revision 1401703) Result = SUCCESS 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
[jira] [Commented] (YARN-180) Capacity scheduler - containers that get reserved create container token to early
[ https://issues.apache.org/jira/browse/YARN-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483259#comment-13483259 ] Robert Joseph Evans commented on YARN-180: -- Thanks for the review Tom, I'll check it in now. Also the port to 0.23 looks clean, a simple refactoring, so +1 for that too. > 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: 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
[jira] [Commented] (YARN-180) Capacity scheduler - containers that get reserved create container token to early
[ https://issues.apache.org/jira/browse/YARN-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482887#comment-13482887 ] Thomas Graves commented on YARN-180: +1 for latest patch. I manually tested this on a small cluster and verified that a container can be reserved for > 10 minutes and the AM can still start the container after finally being allocated it. > 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: 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
[jira] [Commented] (YARN-180) Capacity scheduler - containers that get reserved create container token to early
[
https://issues.apache.org/jira/browse/YARN-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482611#comment-13482611
]
Hadoop QA commented on YARN-180:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12550518/YARN-180.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. 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.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/121//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/121//console
This message is automatically generated.
> 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: 2.0.3-alpha, 0.23.5
>
> Attachments: 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
[jira] [Commented] (YARN-180) Capacity scheduler - containers that get reserved create container token to early
[ https://issues.apache.org/jira/browse/YARN-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482591#comment-13482591 ] Robert Joseph Evans commented on YARN-180: -- Oh I noticed that the containerToken is never assigned anyways. I will fix that too. > 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: 2.0.3-alpha, 0.23.5 > > Attachments: 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
[jira] [Commented] (YARN-180) Capacity scheduler - containers that get reserved create container token to early
[
https://issues.apache.org/jira/browse/YARN-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482589#comment-13482589
]
Robert Joseph Evans commented on YARN-180:
--
The patch looks mostly good. I am a bit confused by {code}if (containerToken ==
null) {
containerToken = null; // Try again later.
}
{code} inside the new createContainerToken method. It is a copy and paste from
before, but not needed any more.
Other then that it looks good. Since Arun is on a plane now I will upload a new
patch.
> 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: 2.0.3-alpha, 0.23.5
>
> Attachments: 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
[jira] [Commented] (YARN-180) Capacity scheduler - containers that get reserved create container token to early
[
https://issues.apache.org/jira/browse/YARN-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13481876#comment-13481876
]
Hadoop QA commented on YARN-180:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12550355/YARN-180.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. 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.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/113//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/113//console
This message is automatically generated.
> 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: 2.0.3-alpha, 0.23.5
>
> Attachments: 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
[jira] [Commented] (YARN-180) Capacity scheduler - containers that get reserved create container token to early
[ https://issues.apache.org/jira/browse/YARN-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13481872#comment-13481872 ] Vinod Kumar Vavilapalli commented on YARN-180: -- It looks like even after container assignment, there are some code paths ( atleast one right below the changes in the patch) where we don't return the assigned container. One simpler approach to token generation is when RMContainerImpl moves to ACQUIRED state. Thoughts? > 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: 2.0.3-alpha, 0.23.5 > > Attachments: 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
[jira] [Commented] (YARN-180) Capacity scheduler - containers that get reserved create container token to early
[ https://issues.apache.org/jira/browse/YARN-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13481802#comment-13481802 ] Vinod Kumar Vavilapalli commented on YARN-180: -- Good catch, Thomas! > 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 > > 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
[jira] [Commented] (YARN-180) Capacity scheduler - containers that get reserved create container token to early
[ https://issues.apache.org/jira/browse/YARN-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13481764#comment-13481764 ] Thomas Graves commented on YARN-180: note that the container token expired causes the AM to fail the launch of the container with error like: 2012-10-20 10:27:15,702 ERROR [ContainerLauncher #70] org.apache.hadoop.mapreduce.v2.app.launcher.ContainerLauncherImpl: Container launch failed for container_1350066773975_81309_01_011780 : RemoteTrace: at LocalTrace: org.apache.hadoop.yarn.exceptions.impl.pb.YarnRemoteExceptionPBImpl: Unauthorized request to start container. This token is expired. current time is 1350728835262 found 1350717961434 at org.apache.hadoop.yarn.ipc.ProtoOverHadoopRpcEngine$Invoker.invoke(ProtoOverHadoopRpcEngine.java:156) at $Proxy30.startContainer(Unknown Source) at org.apache.hadoop.yarn.api.impl.pb.client.ContainerManagerPBClientImpl.startContainer(ContainerManagerPBClientImpl.java:104) at org.apache.hadoop.mapreduce.v2.app.launcher.ContainerLauncherImpl$Container.launch(ContainerLauncherImpl.java:155) at org.apache.hadoop.mapreduce.v2.app.launcher.ContainerLauncherImpl$EventProcessor.run(ContainerLauncherImpl.java:390) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) > 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 > > 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
