On Thu, Sep 17, 2020, at 8:31 AM, Pawel Grzywaczewski wrote:
Hi,
Can someone share some hints about how to deploy redundant and load balanced Mailman3? What are your recommendations and best practices? For example what components to put on the same VM? Can we have 2VM with Mailman core/Postorious/Hyperkitty/django-mailman/mailmanclient connecting to one (the same) database? How to load balance mail routing (incoming)?
The current implementation of Mailman is good for vertical scaling but not that great for horizontal scaling and redundancy.
The web frontend, Postorius & Hyperkitty, are pretty much stateless and can be horizontally scaled and redundantly deployed easily.
I am not going to recommend how to handle redundancy for database, because I am not the best person for that and I honestly don't know anything beyond using a "cloud managed" database from cloud providers for HA.
Mailman Core is a bit hard to run redundantly mostly because of it's reliance on filesystem for some data like email queues, held messages, shunted messages etc. You can potentially have two running instances, one on standby and failover to other instance. You'd need to synchronize the var directory between them using *some* mechanism, rsync or NFS or something. Although, you want to make sure that they both aren't sending out emails at the same time.
Thanks! Paweł
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)