[
https://issues.apache.org/jira/browse/YARN-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xuan Gong updated YARN-3245:
----------------------------
Description: The clean-up container will be launched after the application
is finished/killed/failed. Cleanup container may not get resources if we
negotiate the resource for it separately because cluster may have gotten busy
after the final AM exit. The propose is to reserve AMContainer resource, and
use it to launch clean-up container. In that case, we do not need to
re-negotiate the resource, and clean-up container can be launch in the same NM
as AM. (was: The clean-up container will be launched after the application is
finished/killed/failed. Cleanup container may not get resources if we negotiate
the resource for it separately because cluster may have gotten busy after the
final AM exit. )
> Find a way to reserve AMContainer resource to launch clean-up container in
> CapacityScheduler
> --------------------------------------------------------------------------------------------
>
> Key: YARN-3245
> URL: https://issues.apache.org/jira/browse/YARN-3245
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Xuan Gong
> Assignee: Xuan Gong
>
> The clean-up container will be launched after the application is
> finished/killed/failed. Cleanup container may not get resources if we
> negotiate the resource for it separately because cluster may have gotten busy
> after the final AM exit. The propose is to reserve AMContainer resource, and
> use it to launch clean-up container. In that case, we do not need to
> re-negotiate the resource, and clean-up container can be launch in the same
> NM as AM.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
