[ 
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

Reply via email to