[prev in list] [next in list] [prev in thread] [next in thread] 

List:       info-cyrus
Subject:    Re: High-Availability IMAP server
From:       Wolfgang Powisch <powo+lists.cyrus () powo ! priv ! at>
Date:       2005-09-29 18:16:31
Message-ID: 433C2F7F.4030201 () powo ! priv ! at
[Download RAW message or body]

Scott Adkins wrote:

> --On Monday, September 26, 2005 6:45 PM +0200 David 
> <info-cyrus@mantxado.com> wrote:
>
>> Hello,
>>
>> I have a 'pseudo' High Availability SMTP system consisting in two 
>> servers
>> running cyrus 2.2.5.
>>
>> The main problem I have is that only one of the two nodes can access 
>> to the
>> mailboxes in order to keep the integrity of the cyrus databases 
>> despite the
>> filesystem (GFS) has support to allow to two different servers access 
>> in R/W
>> mode.
>
>
> I am curious about this statement... What kind of locking is being 
> used on
> GFS that prevents two nodes from accessing mailboxes without 
> destroying the
> integrity of the cyrus database?
>
yeah, that's what I asked me too.
Unfortunately I haven't had the chance right now to test such a setup with
multiple cyrus-instances upon the same shared GFS-filesystem.
Both Cyrus instances would use the same databases, only the lock-files 
for the
imapd's and popd's would need to be different I expect.

Has anybody ever had such a setup in production use using Linux and GFS ?
I haven't even tried it, but are very interested in it.

What "integrity"-problem do you mean exactly, David. Have you already 
expirienced
a problem ?

regards

-- 
Wolfgang Powisch <powo@powo.priv.at>
www.powo.priv.at


----
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
[prev in list] [next in list] [prev in thread] [next in thread]