[Mailman-Users] Problems with multi-machine slicing

[Mark Sapiro]

On 05/24/2014 07:52 AM, Jeff Taylor wrote:
> After doing some upgrades, I noticed yesterday that my multi-machine
> setup is no longer properly slicing the queue between machines.  I
> probably missed something, but after going through all my notes on the
> setup I cannot figure out what the problem in.  Hopefully someone else
> can spot the issue?
> 
> I have four mail servers.  Three of them are supposed to slice the queue
> between them, and the fourth machine is set as a backup to process any
> remaining messages after 2 minutes.  On the three slice machines, I have
> patched mailmanctl as:
> ----------
> def start_all_runners():
>     kids = {}
>>>>
>     for qrname, count, machine, nummachines in mm_cfg.QRUNNERS:
>         for slice in range(machine, count, nummachines):
> <<<
>             # queue runner name, slice, numslices, restart count
>             info = (qrname, slice, count, 0)
>             pid = start_runner(qrname, slice, count)
>             kids[pid] = info
>     return kids
> ----------
> 
> Each of these machines has a QRUNNERS section added to mm_cfg.py which
> defines the slice of each machine --  3,0,3  /   3,1,3  / 3,2,3
> and contains the line: QRUNNER_MESSAGE_IS_OLD_DELAY = None


What exactly are the QRUNNERS = assignments in the 3 machines mm_cfg.py
files.

If you do


ps -fwA | grep runner=

on the three machines, what are the --runner= arguments for the sliced
queues?

You should be seeing one of

--runner=IncomingRunner:0:3
--runner=IncomingRunner:1:3
--runner=IncomingRunner:2:3

on each of the 3 machines.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan