Re: Highly available and scalable Cyrus configurations

2003-10-08 Thread Amos Gouaux
> On Tue, 7 Oct 2003 18:43:21 -0400 (EDT), > Rob Siemborski <[EMAIL PROTECTED]> (rs) writes: rs> The key about the usability of the filesystem is that file locks need to rs> be obeyed throughout the entire cluster, and mmap() needs to be efficient rs> (and able to deal with read() and wri

Re: Highly available and scalable Cyrus configurations

2003-10-07 Thread Rob Siemborski
On Tue, 7 Oct 2003, Ben Carter wrote: > > This is not the case. Simple DNS round-robining is sufficient. > > How is simple DNS round-robin sufficient? More than one MUA caches the DNS > lookups for its mail servers. I know that at least one version of > Netscape Communicator used to. It probab

Re: Highly available and scalable Cyrus configurations

2003-10-07 Thread Ben Carter
--On Tuesday, October 07, 2003 6:43 PM -0400 Rob Siemborski <[EMAIL PROTECTED]> wrote:r On Tue, 7 Oct 2003, Ben Carter wrote: and an MTA on each cluster member, because with the murder configuration, you probably have to end up with a load-balancing switch in front of murder front-end machines

Re: Highly available and scalable Cyrus configurations

2003-10-07 Thread Rob Siemborski
On Tue, 7 Oct 2003, Ben Carter wrote: > and an MTA on each cluster member, because with the murder > configuration, you probably have to end up with a load-balancing switch > in front of murder front-end machines which in turn are in front of the This is not the case. Simple DNS round-robining i

Highly available and scalable Cyrus configurations

2003-10-07 Thread Ben Carter
We currently have a single IMAP server and we are considering two Solaris 8/9 HA Cyrus configurations: #1. IMAP Aggregator (murder) #2. Cyrus on a Veritas cluster (common file system with parallel service groups) After looking at the murder design, it seems to me that it's a lot more compli