[
https://issues.apache.org/jira/browse/YARN-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13864212#comment-13864212
]
Steve Loughran commented on YARN-1489:
--------------------------------------
regarding the rebinding problem, YARN-913 proposes some registry where we
restrict the names of services and apps, and require uniqueness. This lets us
register something like (hoya, stevel, accumulo5) and then let a client app
look it up.
Today we have the list of running apps, and you can find and bind to one, but
# there's nothing to stop a single user having >1 instance of the same name
# there's no way for a AM to enumerate this as the list operation isn't in the
AMRM protocol
> [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)
