hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wangda Tan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-3354) Container should contains node-labels asked by original ResourceRequests
Date Fri, 10 Apr 2015 21:29:12 GMT

     [ 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
> 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

View raw message