[YARN-397] RM Scheduler api enhancements

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned Assign to me
• Reporter: Arun Murthy
• Created: 12/Feb/13 05:39
• Updated: 03/Jan/16 01:18

Description

Umbrella jira tracking enhancements to RM apis.

Issue Links

• is blocked by: YARN-45 [Preemption] Scheduler feedback to AM to release containers

Sub-Tasks

• Make it possible to specify hard locality constraints in resource requests: Closed
• In RM * is overloaded for locality as well as resource demand: Open
• RM should be able to return requests that it cannot fulfill: Open
• Enhance CS to allow for white-list of resources: Closed
• AM should have a way of telling RM to not allocate containers on some nodes: Resolved
• RM should have a way to disable scheduling to a set of nodes: Resolved
• Support gang scheduling in the AM RM protocol: Open
• Allow for black-listing resources in YARN API and Impl in CS: Closed
• Allow for black-listing resources in FS: Resolved
• Add multiplier unit to resourcecapabilities: Resolved
• Give apps an idea of totalAppResource: Open
• Allow for black-listing resources in FifoScheduler: Closed
• Schedulers should allow resource requests of different sizes at the same priority and location: Open
• Resource-centric compression in AM-RM protocol limits scheduling: Open
• add ability to specify affinity/anti-affinity in container requests: Open
• Allow for (admin) labels on nodes and resource-requests: Open
• allocate resource on different nodes for task: Resolved
• Providing raw container request information for fine scheduling: Open