Magnus Bergman <[email protected]> wrote: > We are testing policyd on multiple SMTP servers with the same load > balanced master-master replicated MySQL database as backend to be able > to keep quotas synced between different SMTP servers. > > Is this generally a supported setup? > > The reason I am asking is that occationally we are seeing replication > breaking with: > > Duplicate entry '363e.534ea5ea.49a4c.0' for key 'Instance'' on INSERT > INTO session_tracking. > > It seems to be related to a mail from one sender to multiple recipients > and policyd attempting to insert two session_tracking entries with the > same Instance value. If those ends up on different database backends at > about the same time so the two databases are not syncronized we end up > with two conflicting entries.
Yes, in theory it's a supported setup, but without a distributed database that maintains perfect sync then you run the risk of the problem you've observed. Other options are to run multiple policy daemons sharing one database instance, or one policy daemon shared by multiple postfix instances. _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users_lists.policyd.org
