[
https://issues.apache.org/jira/browse/YARN-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sunil G updated YARN-3224:
--------------------------
Attachment: 0002-YARN-3224.patch
Attaching an initial version of patch.
Small summary of this patch:
1. When a node is marked for DECOMMISSIONING, an event will be fired to
Capacity Scheduler to preempt all containers running in that node.
2. In CS, a new event is added for this. And all existing *preemptContainer*
api is invoked for all running container of the node.
Its possible that few AM containers are also marked for preemption. This
current patch gives only a PREEMPT_CONTAINER notification to AM. Timeout is not
added for now as YARN-3784 is yet to be concluded.
[~djp]
Could you please take a look.
> Notify AM with containers (on decommissioning node) could be preempted after
> timeout.
> -------------------------------------------------------------------------------------
>
> Key: YARN-3224
> URL: https://issues.apache.org/jira/browse/YARN-3224
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Junping Du
> Assignee: Sunil G
> Attachments: 0001-YARN-3224.patch, 0002-YARN-3224.patch
>
>
> We should leverage YARN preemption framework to notify AM that some
> containers will be preempted after a timeout.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
