The advice Tyler gave is the correct. Do a rolling upgrade, and shapshot if you
want to have a rollback.
My personal approach is to upgrade a node or two and let run for a few hours.
Just to avoid the situation where you uprade every node and then discover some
problem that causes wailing and
Thanks Aaron. My major concern is upgrade node by node. Because currently we
are using 1.0.6 in production and plan is to upgrade singe node to 1.1.2 at
a time.
Any comments?
Thanks.
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Concerns-about
It's always a good idea to have a read of the NEWS.txt file
https://github.com/apache/cassandra/blob/cassandra-1.1/NEWS.txt
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 12/07/2012, at 5:51 PM, Tyler Hobbs wrote:
> On Wed, Jul 11, 2012 at
On Wed, Jul 11, 2012 at 8:38 PM, Roshan wrote:
>
>
> Currently we are using Cassandra 1.0.6 in our production system but suffer
> with the CASSANDRA-3616 (it is already fixed in 1.0.7 version).
>
> We thought to upgrade the Cassandra to 1.1.X versions, to get it's new
> features, but having some
Hello
Currently we are using Cassandra 1.0.6 in our production system but suffer
with the CASSANDRA-3616 (it is already fixed in 1.0.7 version).
We thought to upgrade the Cassandra to 1.1.X versions, to get it's new
features, but having some concerns about the upgrade and expert advices are
mostl
