[YARN-1582] Capacity Scheduler: add a maximum-allocation-mb setting per queue

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.23.10, 2.2.0, 3.0.0-alpha1
• Fix Version/s: 2.7.0
• Component/s: capacityscheduler
• Target Version/s: 2.7.0
• Hadoop Flags: Reviewed
• Assignee: Thomas Graves
• Reporter: Thomas Graves
• Created: 09/Jan/14 22:33
• Updated: 12/May/16 18:30
• Resolved: 05/Feb/15 19:32

Description

We want to allow certain queues to use larger container sizes while limiting other queues to smaller container sizes. Setting it per queue will help prevent abuse, help limit the impact of reservations, and allow changes in the maximum container size to be rolled out more easily.

One reason this is needed is more application types are becoming available on yarn and certain applications require more memory to run efficiently. While we want to allow for that we don't want other applications to abuse that and start requesting bigger containers then what they really need.

Note that we could have this based on application type, but that might not be totally accurate either since for example you might want to allow certain users on MapReduce to use larger containers, while limiting other users of MapReduce to smaller containers.