hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1489) [Umbrella] Work-preserving ApplicationMaster restart
Date Tue, 07 Jan 2014 16:35:54 GMT

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

Steve Loughran commented on YARN-1489:
--------------------------------------

Actually, the simplest way for an AM to work with a restarted cluster would be if there was
a blocking operation to list active containers. At startup it could get that list and use
it to init its data structures -on a first start the list would be empty.

Alternatively, the restart information could be passed down in {{RegisterApplicationMasterResponse}}
-which would avoid adding any new RPC calls

> [Umbrella] Work-preserving ApplicationMaster restart
> ----------------------------------------------------
>
>                 Key: YARN-1489
>                 URL: https://issues.apache.org/jira/browse/YARN-1489
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Vinod Kumar Vavilapalli
>         Attachments: Work preserving AM restart.pdf
>
>
> Today if AMs go down,
>  - RM kills all the containers of that ApplicationAttempt
>  - New ApplicationAttempt doesn't know where the previous containers are running
>  - Old running containers don't know where the new AM is running.
> We need to fix this to enable work-preserving AM restart. The later two potentially can
be done at the app level, but it is good to have a common solution for all apps where-ever
possible.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message