Right. I have had very few problems running mixed versions for normal operations (as long as the versions are “close”). During upgrades, I turn off repairs. Adding/replacing nodes is very infrequent for me, so not much of a consideration. We upgrade as quickly as we can, however, to protect against issues. Our clusters are not huge, though.
NOTE: the above applies to version 1.0.8, 1.2.x and 2.0.x. The 1.1.x versions are painful and problematic. Sean Durity From: Robert Coli [mailto:rc...@eventbrite.com] Sent: Tuesday, June 09, 2015 6:19 PM To: user@cassandra.apache.org Subject: Re: C* 2.0.15 - java.lang.NegativeArraySizeException On Tue, Jun 9, 2015 at 2:35 PM, Aiman Parvaiz <ai...@flipagram.com<mailto:ai...@flipagram.com>> wrote: Thanks Sean, in this scenario also I would end up running 2 versions of Cassandra as I am planning to do a rolling upgrade and hence zero downtime. Upgrading in place one node at a time would lead to running 2 versions, please let me know if I am missing something here. Running a cluster with nodes of two different versions during a rolling upgrade, for the duration of the upgrade, is (mostly) supported [1]. Modifying cluster topology (adding or removing or replacing nodes) during such an upgrade is not. It is a fair statement that with very large clusters and very slow upgradesstables, the ability of any operator to operate in this manner approaches not-possible. I don't know how people with truly huge clusters deal with this race. =Rob [1] some operations are not supported possible with some combinations of versions. for example one cannot repair in some cases. ________________________________ The information in this Internet Email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this Email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this Email are subject to the terms and conditions expressed in any applicable governing The Home Depot terms of business or client engagement letter. The Home Depot disclaims all responsibility and liability for the accuracy and content of this attachment and for any damages or losses arising from any inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other items of a destructive nature, which may be contained in this attachment and shall not be liable for direct, indirect, consequential or special damages in connection with this e-mail message or its attachment.
