[
https://issues.apache.org/jira/browse/YARN-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Graves updated YARN-180:
-------------------------------
Description:
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.
was:
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 will most likely have expired.
> 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
