You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "German Florez-Larrahondo (JIRA)" <ji...@apache.org> on 2014/01/09 17:59:19 UTC
[jira] [Updated] (YARN-1581) Fair Scheduler: containers that get
reserved create container token to early
[ https://issues.apache.org/jira/browse/YARN-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
German Florez-Larrahondo updated YARN-1581:
-------------------------------------------
Description:
When using the FairScheduler with long running jobs and over-subscribed servers I hit (what I believe is) the same issue reported on https://issues.apache.org/jira/browse/YARN-180 , which talked specifically about the CapacityScheduler:
In my case, with the FairScheduler I am seeing those corner cases when the NodeManager is finally ready to start a container that was reserved but the token was already expired.
was:
When using the FairScheduler with some slow servers and long running jobs I hit (what I believe is) the same issue reported on https://issues.apache.org/jira/browse/YARN-180 , which talked specifically about the CapacityScheduler:
In my case, with the FairScheduler I am seeing those corner cases when the NodeManager is finally ready to start a container that was reserved but the token was already expired.
> Fair Scheduler: containers that get reserved create container token to early
> ----------------------------------------------------------------------------
>
> Key: YARN-1581
> URL: https://issues.apache.org/jira/browse/YARN-1581
> Project: Hadoop YARN
> Issue Type: Bug
> Components: scheduler
> Affects Versions: 2.2.0
> Environment: CentOS 6.4
> Reporter: German Florez-Larrahondo
> Priority: Minor
>
> When using the FairScheduler with long running jobs and over-subscribed servers I hit (what I believe is) the same issue reported on https://issues.apache.org/jira/browse/YARN-180 , which talked specifically about the CapacityScheduler:
> In my case, with the FairScheduler I am seeing those corner cases when the NodeManager is finally ready to start a container that was reserved but the token was already expired.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)