HelloIf you can guarantee, that a user is always routed to the same sogo backend server, then you can use one memcached per server.
Else you will get random errors, when changing data or writing emails.
Kind regards, Christian Mack Am 10.04.26 um 11:34 schrieb "Alexey D. Filimonov" ([email protected]):
Could you please explain is it critical for SOGo to use common memcached, or it is just a performance question? I'm thinking about to make each instance to have it's own memcached, not distributedI will have one single web client per day from single ip that is mapped through balancer to single SOGo instance, and no other clients expected.09.12.2024 19:53, qhivert ([email protected]) пишет:Hello, Yes, sogo nodes should use a common Memcached.You should also have a shared volume (nfs) for the parameter SOGoMailSpoolPath (default to /var/spool/sogo).Quentin -----Original Message-----From: [email protected] <[email protected]> On Behalf Of "Alexey D. Filimonov"Sent: lundi 9 décembre 2024 17:48 To: [email protected] Subject: [SOGo] SOGo clustering question Can not find about anything related clustering SOGo.Could you please help me if SOGo nodes should use common memcached or each should use it's own?
-- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre, Infrastruktur 78457 Konstanz +49 7531 88-4416
smime.p7s
Description: Kryptografische S/MIME-Signatur
