Well, that is certainly a wealth of information from you two, thanks a ton! I've got a few things to try now.
I'm going to have to look up the retry runner to see if that might help when we have to shut things down.
I'll let you know what I find...
On Tue, Apr 10, 2018 at 5:41 PM, Mark Sapiro <mark@msapiro.net> wrote:
Yes, this is a known thing and the reason for it is that the SIGTERM isn't delivered till the process wakes up next time. We can have the
On 04/10/2018 03:39 PM, Abhilash Raj wrote: process sleep for a smaller amount of time to fix this, but then it would mean that it will be running much more often.
It is the Retry runner, which has sleep_time set to 15m. I don't know if
you want to retry very often, like 2min or 5min, but you can change it by adding the following snippet to your mailman.cfg
A long time ago (in a galaxy far away) Mailman 2.1 had a global DELIVERY_RETRY_WAIT setting. This setting had been ineffective for years, relying instead on the retry runner's sleep time.
In 2.1.26, for what turned out to be a probably spurious reason, I made DELIVERY_RETRY_WAIT effective again, although the retry runner still sleeps for 15 minutes.
We could implement something similar in MM 3 to allow the retry runner to have a much shorter sleep time without actually retrying the delivery that often. The down side of that is even though we aren't retrying delivery each time the runner wakes up, we are dequeueing and requeueing the message each time and this would have a file system impact.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/