Thanks for fast response Abhilash!
See inline for responses:
On 3/18/19 9:24 AM, Abhilash Raj wrote:
On Mon, Mar 18, 2019, at 9:14 AM, Dmitry Makovey wrote:
In the last couple of month we've observed some odd behavior from MM3 (namely the core) where it seems like email that is about to be sent to a large-ish mailing list (10K users) has been processed yet never gets sent out until we restart the core.
This is indeed weird, I don't think 10k is too much, but it also depends on your MTA. How fast do they allow sending emails and if there is any rate limiting.
I'm using Mailu.io for MTA. We're controlling it so there's not much throttling as I've whitelisted mailman to send anything over LMTP.
I wouldn't necessarily consider this a performance problem in Core, since it is still just processing only one email. All it needs to do is send them all out, which is where the problem should be.
inferred assumption is that mailman-core loses LMTP connection with Mailu stack. but then upon restart of service it regains it?
I'd imagine debug logging on outgoing runner should give some more pointers on what is going on.
You can configure the smtp runner to log extra information (copied from docs)1
awesome - I'll give it a go. thanks for the pointer.
I'd also recommend looking into MTA logs for anything un-usual.
we briefly did , but nothing stood out.
troubleshooting/digging before I just restart the core (which by the way takes about 45min to fully start... which is another puzzle to solve at
How do you measure that it takes 45 mins to start?
normally it's "docker ps" command output along with "docker top" so once I see all the sub-processes kicked off I'm assuming core is started and from that point it's anywhere between 35 and 45min before I can get any *response* from core (i.e. mailman-web complains, REST commands fail, etc.)
What database backend are you using?
Postgres. The whole setup is docker-setup (0.1.7 version of containers at this point).
-- Sr System and DevOps Engineer SoM IRT