On Sat, 18 Mar 2006, Mark wrote:
Thanks Patrick. The reason we want to speed up the upgrades is because of the
2.2.12 threading problems - high cpu, locked up mupdate. Ideally we would
upgrade mupdate to 2.3.x and then upgrade the front ends and back ends a little
later. Do you think 2.3 mupdate would work well with 2.2.12 backends?
2.2.12 backends should work with a 2.3 murder master. I don't think there
have been changes to the mupdate protocol.
What mupdate problems are you seeing with 2.3?
Pretty much what Alek said, but on a less frequent basis. We'd see it when
there were too many simultanious mailbox creations and/or a frontend was
restarted when the murder master was under load.
Mark
Patrick H Radtke <[EMAIL PROTECTED]> wrote: We have 2.2.12 frontends, 2.3
backends and 2.3 murder master.
Only reason we went with 2.2.12 for frontends is that when we first
installed 2.3 it was in the summer and 2.3 didn't work as a frontend. That
has been fixed now. Only reason we haven't changed the frontends to 2.3 is
that we're busy with other stuff at the moment.
There are some problems with the murder master in 2.3. We use it anyways
since it fixes some threading problems that would occur in 2.2.12
-Patrick
On Sat, 18 Mar 2006, Mark wrote:
Hello,
I'm looking for a (conservative) upgrade path from 2.2.12 to 2.3.3, and was
wondering if anyone ran cyrus murder with mixed imapd versions. For example,
2.2.12 back ends, 2.3.3 mupdate server (it is 2.2.12 now) and 2.2.12 front
ends. Or, if anyone did the upgrades from 2.2.x to 2.3.x in another way, would
you mind sharing your thoughts.
Thanks for any suggestions.
Mark
---------------------------------
Brings words and photos together (easily) with
PhotoMail - it's free and works with Yahoo! Mail.
----
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
