Every so often, one of our spamd instances gets locked up when a burst
of messages with "lots" (150-200K+) of body text gets passed in.
If we catch this happening, restarting spamd seems to clear up whatever
gets deadlocked. Otherwise, it typically takes 10-15 minutes to get
unlocked, and then there's a big burst of processing as the backlog clears.
Has anyone else seen anything like this?
Is this possibly something entirely internal to spamd?
Is this a Bayes update deadlock? (We use a global Bayes DB, currently
MySQL ISAM tables on a tmpfs.) Testing just before migrating to the
current hardware showed this was actually the *fastest* (and least
I/O-intensive) setup (comparing with InnoDB tables on disk, or "memory"
tables).
-kgd
