[
https://issues.apache.org/jira/browse/YARN-926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13711642#comment-13711642
]
Jian He commented on YARN-926:
------------------------------
bq. should stopContainer take the request of multiple containers as well
yes, we'll do this for startContainer/stopContainer/getContainerStatus.
After offline discussion with Vinod, Omkar, Bikas, Hitesh, we come up with the
following new record structures
StartContainersRequest:
- a list of StartContainerRequest
StartContainersResponse:
- a list of servicesMetaData
- a list of ContainerIds for succeeded requests
- a list of ContainerId to Exception Map for failed requests
StopContainersRequest:
- a list of containerIds to be stopped
StopContainersResponse:
- a list of ContainerIds for succeeded requests
- a list of ContainerId to Exception Map for failed requests
GetContainerStatusesRequest:
- a list of containerIds to be queried
GetContainerStatusesResponse:
- a list of ContainerId to ContainerStatus Map for succeeded requests
- a list of ContainerId to Exception Map for failed requests
> ContainerManagerProtcol APIs should take in requests for multiple containers
> ----------------------------------------------------------------------------
>
> Key: YARN-926
> URL: https://issues.apache.org/jira/browse/YARN-926
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Jian He
> Priority: Blocker
>
> AMs typically have to launch multiple containers on a node and the current
> single container APIs aren't helping. We should have all the APIs take in
> multiple requests and return multiple responses.
> The client libraries could expose both the single and multi-container
> requests.
--
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
