[YARN-1004] yarn.scheduler.minimum|maximum|increment-allocation-mb should be prefixed with the scheduler type

• Type: Improvement
• Status: Closed
• Priority: Blocker
• Resolution: Won't Fix
• Affects Version/s: 2.1.0-beta
• Fix Version/s: 2.1.0-beta
• Component/s: scheduler
• Assignee: Unassigned
• Reporter: Sandy Ryza
• Created: 31/Jul/13 07:46
• Updated: 27/Aug/13 22:15
• Resolved: 15/Aug/13 22:06

Description

As yarn.scheduler.minimum-allocation-mb is now a scheduler-specific configuration, and functions differently for the Fair and Capacity schedulers, it would be less confusing for the config names to include the scheduler names, i.e. yarn.scheduler.fair.minimum-allocation-mb, yarn.scheduler.capacity.minimum-allocation-mb, and yarn.scheduler.fifo.minimum-allocation-mb.

The same goes for yarn.scheduler.increment-allocation-mb, which only exists for the Fair Scheduler, and yarn.scheduler.maximum-allocation-mb, for consistency.

If we wish to preserve backwards compatibility, we can deprecate the old configs to the new ones.

Issue Links

• duplicates: YARN-1009 Scheduler configuration properties should be prefixed with the scheduler type