Is it safe to upgrade between minor releases without first performing a repair?

[Jerry <je...@gmail.com>]

In general it seems that repairs should be done prior to every upgrade (in
fact they should be done at least weekly), but with a minor upgrade like
this is it safe to upgrade without first repairing?

Specifically, I'm looking to upgrade from Cassandra 2.0.11 to 2.0.17.

Re: Is it safe to upgrade between minor releases without first performing a repair?

[Mateusz Korniak <ma...@ant.gliwice.pl>]

On Thursday 20 of July 2017 23:27:55 Jerry wrote:
> In general it seems that repairs should be done prior to every upgrade (in
> fact they should be done at least weekly), but with a minor upgrade like
> this is it safe to upgrade without first repairing?

Depends on meaning of "is it safe" ... 

> Specifically, I'm looking to upgrade from Cassandra 2.0.11 to 2.0.17.

This is bugfix only upgrade, so in general Cassandra should perform only 
better _after_ upgrade.

On other hand, _during_ upgrade, you have to restart all nodes. Assuming 
having data inconsistency among nodes, you may get different query results 
(old/missing data, etc...) during node restarts.


-- 
Mateusz Korniak
"(...) mam brata - poważny, domator, liczykrupa, hipokryta, pobożniś,
 	krótko mówiąc - podpora społeczeństwa."
				Nikos Kazantzakis - "Grek Zorba"


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
For additional commands, e-mail: user-help@cassandra.apache.org