Considering how the code has turned out, the Capacity Scheduler iterates over queues it gets from the framework's QueueManager class. Now, when it asks the CapacitySchedulerConf for a property for this queue, if nothing is configured for this queue in capacity-scheduler.xml, a hard-coded default value is returned. This may not be what the administrator intended, because the defaults are not defined by him/her. Hence, this issue exists.
HADOOP-4178 is trying to implement a mechanism to make these default values itself configurable. If it does that, then it would be a feature that if a property is not configured for a queue in the capacity scheduler's configuration, the configured default is used. This makes it very simple for the administrator to define new queues. And it would invalidate the need to check for invalid queues, as required by this issue.
So in summary, if
HADOOP-4178 is fixed, we can mark this bug as invalid. Comments ?