[
https://issues.apache.org/jira/browse/YARN-7565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16279381#comment-16279381
]
Chandni Singh edited comment on YARN-7565 at 12/6/17 12:26 AM:
---------------------------------------------------------------
Patch 2
- Addressed [~jianhe]'s comments
- Instead of checking repeatedly if containers are recovered, made the change
in ServiceScheduler to check just once if the unRecovered containers are still
there. If they haven't been recovered by then, then the container is released
and component instance is added to pending queue.
- Added another test
was (Author: csingh):
Patch 2
- Addressed [~jianhe]'s comments
- Instead of checking repeatedly if containers are recovered, made the change
in ServiceScheduler to check just once if the unRecovered containers are
available.
- Added another test
> Yarn service pre-maturely releases the container after AM restart
> ------------------------------------------------------------------
>
> Key: YARN-7565
> URL: https://issues.apache.org/jira/browse/YARN-7565
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Chandni Singh
> Assignee: Chandni Singh
> Fix For: yarn-native-services
>
> Attachments: YARN-7565.001.patch, YARN-7565.002.patch
>
>
> With YARN-6168, recovered containers can be reported to AM in response to the
> AM heartbeat.
> Currently, the Service Master will release the containers, that are not
> reported in the AM registration response, immediately.
> Instead, the master can wait for a configured amount of time for the
> containers to be recovered by RM. These containers are sent to AM in the
> heartbeat response. Once a container is not reported in the configured
> interval, it can be released by the master.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
