hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1417) RM may issue expired container tokens to AM while issuing new containers.
Date Tue, 26 Nov 2013 23:58:35 GMT

    [ https://issues.apache.org/jira/browse/YARN-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13833242#comment-13833242
] 

Vinod Kumar Vavilapalli commented on YARN-1417:
-----------------------------------------------

YARN-180 fixed this for CapacityScheduler, seems like FairScheduler is what needs fixing.

I like the overall approach though, this was what I kinda suggested at YARN-180 but it wasn't
done that way. +1 for the approach. Tests?

> 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: Omkar Vinit Joshi
>            Priority: Blocker
>         Attachments: YARN-1417.2.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#6144)

Mime
View raw message