Hello, does anyone run multiple instances of Cluebringer sharing a database?
I tried to run Cluebringer (dev version) on two mailservers using a master-master MySQL setup. I kept running into SQL problems, for example if a spammer tries to deliver the same mail to both our mailservers at the same time than both servers will try to insert the same row into the database and one will be refused or the database will go out-of-sync. To solve this I adjusted some of the MySQL-queries to deal better with existing data. This solved most problems but not all, as I'm no SQL-expert I had to switch MySLQ to master-slave to get rid of the last synchronisation issues. This solution has worked fine for a few weeks but I was expecting Cluebringer to work out-of-the box in this scenario. As Cluebringer uses multiple threads these problems should also occur on systems using only a single machine but I never experienced any. Maybe because the mailserver accepts only a limited amount of connections per sender. Before forwarding my patches I would like to make sure that I didn't miss anything. Does anyone run Cluebringer on multiple servers? What are your experiences? Which database-backend do you use? If it's MySQL, how do you deal with HA/redundancy? Any advice on or best practices for running multiple Cluebringer instances? -- Casper Gielen <[email protected]> | LIS UNIX PGP fingerprint = 16BD 2C9F 8156 C242 F981 63B8 2214 083C F80E 4AF7 Universiteit van Tilburg | Postbus 90153, 5000 LE Warandelaan 2 | Telefoon 013 466 4100 | G 236 | http://www.uvt.nl
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users_lists.policyd.org
