You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Wangda Tan (JIRA)" <ji...@apache.org> on 2015/04/10 23:29:12 UTC

[jira] [Updated] (YARN-3354) Container should contains node-labels asked by original ResourceRequests

     [ https://issues.apache.org/jira/browse/YARN-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wangda Tan updated YARN-3354:
-----------------------------
    Attachment: YARN-3354.1.patch

Attached ver.1 patch, includes:
- Set RMContainer.requiredNodeLabelExpression when allocating
- Be able to recovery requiredNodeLabelExpression upon RM restart.

> Container should contains node-labels asked by original ResourceRequests
> ------------------------------------------------------------------------
>
>                 Key: YARN-3354
>                 URL: https://issues.apache.org/jira/browse/YARN-3354
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: api, capacityscheduler, nodemanager, resourcemanager
>            Reporter: Wangda Tan
>            Assignee: Wangda Tan
>         Attachments: YARN-3354.1.patch
>
>
> We proposed non-exclusive node labels in YARN-3214, makes non-labeled resource requests can be allocated on labeled nodes which has idle resources.
> To make preemption work, we need know an allocated container's original node label: when labeled resource requests comes back, we need kill non-labeled containers running on labeled nodes.
> This requires add node-labels in Container, and also, NM need store this information and send back to RM when RM restart to recover original container.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)