On Fri, Jan 26, 2007 at 12:07:49AM -0800, Tom Samplonius wrote: > > ----- Janne Peltonen <janne.peltonen@xxxxxxxxxxx> wrote: > > Hi! > > > > As a part of our clustering Cyrus system, we are considering using > > replication to prevent a catastrophe in case the volume used by the > > cluster gets corrupted. (We'll have n nodes each accessing the same GFS, > > and yes, it can be done, see previous threads on the subject.) > > I really doubt this. Even if GFS works the way it says it does, > Cyrus does not expect to see other instances modifying the same > message, and does not lock against itself. I'm not entering this discussion again. ;) There are long threads on this subject, especially since last October. See the archives. >[...] > The Cyrus master builds a replication log as changes are made by > imapd, pop3d, and lmtpd. The log contents are pushed to the > replica. OK. Thanks. --Janne ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
