Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 23 Oct 2012 19:51:13 +0000 (UTC)
From: "Thomas Graves (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <518935378.17672.1351021873306.JavaMail.jiratomcat@arcas>
In-Reply-To: <1183381431.11990.1350936013519.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (YARN-180) Capacity scheduler - containers that
 get reserved create container token to early
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/YARN-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Graves updated YARN-180:
-------------------------------

    Attachment: YARN-180-branch_0.23.patch

here is the same patch but for branch-0.23 since it didn't apply cleanly.
                
> 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