Michael Grant <michael.gr...@gmail.com> writes: > I did not realize one could store the bayes scores in sql. > > So I'd store the bayes scores on a third server and let both mxes use > the same database.
I did this, but my bayes in mysql and pointed two different spamd machines at it, but I had severe problems that I could not resolve. I posted to the list[0] about the problems. The basic problem was that as soon as I fired up the second server it immediately starts blocking on the bayes work. Average scantimes go from 1-2 seconds up to 35+ and the max children get eaten up by blocking on the bayes work to the point where its pointless because too many processes are blocked. Disabling the bayes_sql stuff on one of the machines dropped the scantimes back to their expected average of 1-2 seconds (but of course none of the BAYES tests will fire and autolearning fails). My mysql server is its own machine, it was local to the first spamd (local LAN) and remote to the second (over the net). I eliminated any hostname lookup problems, obviously couldn't eliminate network latency, but that shouldn't have caused such a severe result. I'm running with InnoDB tables, so I shouldn't have any row-level locking issues... in any case I might have had some issues because my MySQL database needed to be optimized, but I was not able to determine how and now I just run one of the spamd's without bayes, which is not too bad because my bayes database seems to be totally worthless at the moment. :P micah 0. http://permalink.gmane.org/gmane.mail.spam.spamassassin.general/113673
