Merto, Are you looking to disable all undefined pools completely, preventing submissions to it? For that, "mapred.fairscheduler.allow.undeclared.pools" needs to be set to false.
On Wed, Mar 14, 2012 at 1:36 AM, Merto Mertek <masmer...@gmail.com> wrote: > Thanks for your workaround, but I think that with this you just put a > constraint on the pool that it will not accept any job. I am doing some > calculation with weights and do not want the default pool weight to be > included in the computation.. > > > On 13 March 2012 18:52, Jean-Daniel Cryans <jdcry...@apache.org> wrote: > >> We do it here by setting this: >> >> <poolMaxJobsDefault>0</poolMaxJobsDefault> >> >> So that you _must_ have a pool (that's configured with a different >> maxRunningJobs) in order to run jobs. >> >> Hope this helps, >> >> J-D >> >> On Tue, Mar 13, 2012 at 10:49 AM, Merto Mertek <masmer...@gmail.com> >> wrote: >> > I know that by design all unmarked jobs goes to that pool, however I am >> > doing some testing and I am interested if is possible to disable it.. >> > >> > Thanks >> -- Harsh J
