[
https://issues.apache.org/jira/browse/YARN-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13865223#comment-13865223
]
Steve Loughran commented on YARN-1041:
--------------------------------------
Looks good as an API for an AM to work with
# there's a lot of duplication across each scheduler's {{
getAllRunningContainers()}} -could it be stuck somewhere shared?
# I get the impression that the protobuf response when there are no running
containers in {{null}}. An empty list would be more elegant AM-side as it
wouldn't need to ever check for null/have a risk of NPEs
> Protocol changes for RM to bind and notify a restarted AM of existing
> containers
> --------------------------------------------------------------------------------
>
> Key: YARN-1041
> URL: https://issues.apache.org/jira/browse/YARN-1041
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Affects Versions: 3.0.0
> Reporter: Steve Loughran
> Assignee: Jian He
> Attachments: YARN-1041.1.patch
>
>
> For long lived containers we don't want the AM to be a SPOF.
> When the RM restarts a (failed) AM, it should be given the list of containers
> it had already been allocated. the AM should then be able to contact the NMs
> to get details on them. NMs would also need to do any binding of the
> containers needed to handle a moved/restarted AM.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
