[EMAIL PROTECTED] wrote:
>
> I built an IMAP cluster some weeks ago that tried to address the sacling
> problem somewhat different.
Looks nice.
> A. Each node has direct access to its storage via SCSI/Fiberchannel bus.
Perfect but very expensive, especially if you go with fiberchannel.
>
> B. Each node has a backup system with the same access (the storage is
> sort of a SAN and administered by the kimberlite clustering software).
> The backup system will access the devices only on failover situations
> and will then replace the original system.
Could you elaborate on that a bit?
> C. Each node has therefore its own user space. As the Cyrus IMAP software
> cannot talk to others over several nodes which user is where, we used
> a separate Linux cluster at the front to proxy every incoming user
> request to its respective Cyrus IMAP server. We used perdition as the
> proxy and an LDAP server as the main user base. Every user within
> the LDAP is marked to which node he belongs to.
The Linux cluster that you use at the front to proxy every incoming connection
is redundant? How did you set it up? Did you use some High Availability patches?
Aside from that, congratulations. It seems you have a very powerful setup :)
Haim
http://dudle.linuxroot.org
