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 "Jian He (JIRA)" <ji...@apache.org> on 2014/02/12 19:25:23 UTC
[jira] [Updated] (YARN-1417) RM may issue expired container tokens
to AM while issuing new containers.
[ https://issues.apache.org/jira/browse/YARN-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jian He updated YARN-1417:
--------------------------
Attachment: YARN-1417.3.patch
Patch that sets container token only when the container is pulled by the AM and adds the unit test.
> RM may issue expired container tokens to AM while issuing new containers.
> -------------------------------------------------------------------------
>
> Key: YARN-1417
> URL: https://issues.apache.org/jira/browse/YARN-1417
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Omkar Vinit Joshi
> Assignee: Jian He
> Priority: Blocker
> Attachments: YARN-1417.2.patch, YARN-1417.3.patch
>
>
> Today we create new container token when we create container in RM as a part of schedule cycle. However that container may get reserved or assigned. If the container gets reserved and remains like that (in reserved state) for more than container token expiry interval then RM will end up issuing container with expired token.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)