hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-562) NM should reject containers allocated by previous RM
Date Fri, 12 Apr 2013 21:36:16 GMT

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

Jian He updated YARN-562:
-------------------------

    Attachment: YARN-562.1.patch

This patch does:
1. add RM's cluster timestamp in NM to reject old containers.
2. Block container requests while NM is resyncing with RM.
3. Add test cases for both cases

                
> NM should reject containers allocated by previous RM
> ----------------------------------------------------
>
>                 Key: YARN-562
>                 URL: https://issues.apache.org/jira/browse/YARN-562
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Jian He
>            Assignee: Jian He
>         Attachments: YARN-562.1.patch
>
>
> Its possible that after RM shutdown, before AM goes down,AM still call startContainer
on NM with containers allocated by previous RM. When RM comes back, NM doesn't know whether
this container launch request comes from previous RM or the current RM. we should reject containers
allocated by previous RM 

--
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

Mime
View raw message