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-3361) CapacityScheduler side changes to support non-exclusive node labels
Date Fri, 10 Apr 2015 20:47:12 GMT

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

Wangda Tan updated YARN-3361:
-----------------------------
    Attachment: YARN-3361.9.patch

bq. how about missedNonPartitionedRequestSchedulingOpportunity -> numNonPartitionedRequestSkipped
?, similarly for the code comments and APIs
Actually it's *number of missed scheduling opportunity* instead of *number of skipped ResourceRequest*.
I prefer to keep it as-is.

bq. fix the copied comments for {{ Multiset<Priority> missedNonPartitionedRequestSchedulingOpportunity
= HashMultiset.create(); }},
Done

bq. fix copied comment for resetMissedNonPartitionedRequestSchedulingOpportunity
Done

bq. getRunningContainer in SchedulerNode not used, remove
Done

bq. typo
Done

Attached ver.9 patch.

> CapacityScheduler side changes to support non-exclusive node labels
> -------------------------------------------------------------------
>
>                 Key: YARN-3361
>                 URL: https://issues.apache.org/jira/browse/YARN-3361
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacityscheduler
>            Reporter: Wangda Tan
>            Assignee: Wangda Tan
>         Attachments: YARN-3361.1.patch, YARN-3361.2.patch, YARN-3361.3.patch, YARN-3361.4.patch,
YARN-3361.5.patch, YARN-3361.6.patch, YARN-3361.7.patch, YARN-3361.8.patch, YARN-3361.9.patch
>
>
> According to design doc attached in YARN-3214, we need implement following logic in CapacityScheduler:
> 1) When allocate a resource request with no node-label specified, it should get preferentially
allocated to node without labels.
> 2) When there're some available resource in a node with label, they can be used by applications
with following order:
> - Applications under queues which can access the label and ask for same labeled resource.

> - Applications under queues which can access the label and ask for non-labeled resource.
> - Applications under queues cannot access the label and ask for non-labeled resource.
> 3) Expose necessary information that can be used by preemption policy to make preemption
decisions.



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

Mime
View raw message