Re: Running repair while Cassandra upgrade 2.0.X to 2.1.X

That ticket says that streaming SSTables that are older versions is supported. Streaming is only one component of repairs, and this ticket doesn't talk about repair at all, only bootstrap. For the most part it should work but as Alain said, it's probably best avoided. Especially if you can avoid

Re: Running repair while Cassandra upgrade 2.0.X to 2.1.X

Thanks Alain !! During Cassandra upgrade, we halt repair scheduling for 24 hours as this is good time to finish upgradesstables..we dont want continuous manual monitoring of upgradesstables and then rescheduling of repair tasks when upgradesstables successfully finishes on all the nodes..Here is

Re: Running repair while Cassandra upgrade 2.0.X to 2.1.X

Hi Shini, First thing that comes to my mind honestly is "why?". Why would you do this? It's way safer to finish upgrade then repair I would say. That being said, I can make guesses for you here, but the best would probably be to test it. 1. Running nodetool repair on one of the nodes while

Re: Running repair while Cassandra upgrade 2.0.X to 2.1.X

Hi Can someone please answer this query? Thanks On Wed, Dec 6, 2017 at 9:58 AM, shini gupta wrote: > If we have upgraded Cassandra binaries from 2.0 to 2.1 on ALL the nodes > but upgradesstable is still pending, please provide the impact of following > scenarios: > > > >

Running repair while Cassandra upgrade 2.0.X to 2.1.X

If we have upgraded Cassandra binaries from 2.0 to 2.1 on ALL the nodes but upgradesstable is still pending, please provide the impact of following scenarios: 1. Running nodetool repair on one of the nodes while upgradesstables is still executing on one or more nodes in the cluster. 2. Running