Re: Cyrus 'cluster' general upgrade strategy?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



You'll need to upgrade primary and replica backends together for a 2.3.7 to 2.3.8 upgrade. Other than that, you can upgrade just one backend pair in a 2.3.7 cluster, no problem. Once you have confidence in the correctness of 2.3.8, upgrade the rest of the backends. It's also pretty common to mix 2.3.x backends with 2.2.x frontends and/or master.

:wes

On 15 May 2007, at 14:24, Nik Conwell wrote:
For those with medium to large scale murders or other glued together clusters of cyrus servers, what's the general strategy for upgrading?

Do you take downtime for the entire cluster and upgrade, or do you roll through upgrades of the parts?

The latter would be prudent, except that I discovered you can't replicate 2.3.7 to 2.3.8 (CREATE has an extra argument at 2.3.8) so it wouldn't surprise me if it generally isn't considered a good idea to mix versions like this in a murder.
----
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

[Index of Archives]     [Cyrus SASL]     [Squirrel Mail]     [Asterisk PBX]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [KDE]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux