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] [Commented] (YARN-4470) Application Master in-place upgrade
Date Tue, 29 Dec 2015 23:31:49 GMT

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

Jian He commented on YARN-4470:
-------------------------------

My concern on this is that a lot of complexity is added into app/attempt state machine, which
is already very complex. 
IIUC, all you need is a way to have the client be able to restart AM with a new ApplicationSubmissionContext.

YARN-261 already adds the ability to kill and restart current attempt, we can leverage that
code path and provide a new AppSubmissionContext to the app


> Application Master in-place upgrade
> -----------------------------------
>
>                 Key: YARN-4470
>                 URL: https://issues.apache.org/jira/browse/YARN-4470
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: resourcemanager
>            Reporter: Giovanni Matteo Fumarola
>            Assignee: Giovanni Matteo Fumarola
>         Attachments: AM in-place upgrade design. rev1.pdf
>
>
> It would be nice if clients could ask for an AM in-place upgrade.
> It will give to YARN the possibility to upgrade the AM, without losing the work
> done within its containers. This allows to deploy bug-fixes and new versions of the AM
incurring in long service downtimes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message