Hi, I ended up finding another post about the exact same issue on this exact same mailing list, that was just a few days old...
It looks like the setting to play with is mapred.capacity-scheduler.default-user-limit-factor Sami On Thu, Oct 20, 2011 at 1:25 PM, Sami Dalouche <sa...@hopper.com> wrote: > Hi, > > By choosing the capacity scheduler, I was under the impression that each > queue could borrow other queues' resources if they are available. > > > Let's say we have the configuration below, and a total capacity of 180 > slots. > What I expect is that whenever default and cpu-bound queues have no job, > then jobs submitted to io-bound should be able to borrow up to 90 slots (50% > total capacity). > However, it looks like it never gets above 59 slots (33% of 180 slots). > > Is there something I missed ? > Thanks, > Sami Dalouche > > --- > <property> > <name>mapred.capacity-scheduler.queue.default.capacity</name> > <value>33</value> > </property> > <property> > <name>mapred.capacity-scheduler.queue.default.maximum-capacity</name> > <value>50</value> > </property> > <property> > <name>mapred.capacity-scheduler.queue.default.supports-priority</name> > <value>true</value> > </property> > > <!-- queue: io-bound --> > <property> > <name>mapred.capacity-scheduler.queue.io-bound.capacity</name> > <value>33</value> > </property> > <property> > > <name>mapred.capacity-scheduler.queue.io-bound.maximum-capacity</name> > <value>50</value> > </property> > <property> > > <name>mapred.capacity-scheduler.queue.io-bound.supports-priority</name> > <value>true</value> > </property> > > <!-- queue: cpu-bound --> > <property> > <name>mapred.capacity-scheduler.queue.cpu-bound.capacity</name> > <value>34</value> > </property> > <property> > > <name>mapred.capacity-scheduler.queue.cpu-bound.maximum-capacity</name> > <value>100</value> > </property> > <property> > > <name>mapred.capacity-scheduler.queue.cpu-bound.supports-priority</name> > <value>true</value> > </property> > >
