[YARN-314] Schedulers should allow resource requests of different sizes at the same priority and location

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.0.2-alpha
• Component/s: scheduler
• Assignee: Unassigned
• Reporter: Sandy Ryza
• Created: 04/Jan/13 07:38
• Updated: 09/Jun/16 21:05

Description

Currently, resource requests for the same container and locality are expected to all be the same size.

While it it doesn't look like it's needed for apps currently, and can be circumvented by specifying different priorities if absolutely necessary, it seems to me that the ability to request containers with different resource requirements at the same priority level should be there for the future and for completeness sake.

Issue Links

• blocks: REEF-42 Extra YARN container causing unexpected memory reservations
• depends upon: YARN-4879 Enhance Allocate Protocol to Identify Requests Explicitly
• relates to: TWILL-73 Unable to allocate small container after large container has been acquired
• relates to: TEZ-3296 Tez job can hang if two vertices at the same root distance have different task requirements