Re: [EXTERNAL] Cassandra 3.11.X upgrades

There isn't any Rollback in real time systems. It's better to test upgrade sstables and binary on one node. Then - if it was OK, upgrade binary on all nodes then run upgrade sstables one server at a time. OR - If it was OK, upgrade servers (binary+sstables) one by one. *---

RE: [EXTERNAL] Cassandra 3.11.X upgrades

: Erick Ramirez Sent: Tuesday, March 3, 2020 11:35 PM To: user@cassandra.apache.org Subject: Re: [EXTERNAL] Cassandra 3.11.X upgrades Should upgradesstables not be run after every node is upgraded? If we need to rollback then we will not be able to downgrade sstables to older version You can

Re: [EXTERNAL] Cassandra 3.11.X upgrades

> > Should upgradesstables not be run after every node is upgraded? If we need > to rollback then we will not be able to downgrade sstables to older version > You can choose to (a) upgrade the SSTables one node at a time as you complete the binary upgrade, or (b) upgrade the binaries on all nodes

Re: [EXTERNAL] Cassandra 3.11.X upgrades

Manish is correct. Upgrade the Cassandra version of a single node only. If that node is behaving as expected (i.e. is in an Up/Normal state and no errors in the logs), then upgrade the Cassandra version for each node one at a time. Be sure to check that each node is running as expected. Once the C

Re: [EXTERNAL] Cassandra 3.11.X upgrades

Should upgradesstables not be run after every node is upgraded? If we need to rollback then we will not be able to downgrade sstables to older version. Regards Manish On Tue, Mar 3, 2020 at 11:26 PM Hossein Ghiyasi Mehr wrote: > It's more safe to upgrade one node before upgrading another node

Re: [EXTERNAL] Cassandra 3.11.X upgrades

It's more safe to upgrade one node before upgrading another node to avoid down time. After upgrading binary and package, run upgradesstables on candidate node then do it on all cluster nodes one by one. *---* *VafaTech :

Re: [EXTERNAL] Cassandra 3.11.X upgrades

- Verify that nodetool upgradesstables has completed successfully on all nodes from any previous upgrade - Turn off repairs and any other streaming operations (add/remove nodes) - Nodetool drain on the node that needs to be stopped (seeds first, preferably) - Stop an un-upgraded n

RE: [EXTERNAL] Cassandra 3.11.X upgrades

+1 on nodetool drain. I added that to our upgrade automation and it really helps with post-upgrade start-up time. Sean Durity From: Erick Ramirez Sent: Wednesday, February 12, 2020 10:29 PM To: user@cassandra.apache.org Subject: Re: [EXTERNAL] Cassandra 3.11.X upgrades Yes to the steps. The

Re: [EXTERNAL] Cassandra 3.11.X upgrades

Yes to the steps. The only thing I would add is to run a nodetool drain before shutting C* down so all mutations are flushed to SSTables and there won't be any commit logs to replay on startup. Also, the usual "backup your cluster and configuration files" boilerplate applies. 😁 >

Re: [EXTERNAL] Cassandra 3.11.X upgrades

Should I follow the steps above right? Thanks Erick! On Wed, Feb 12, 2020, 6:58 PM Erick Ramirez wrote: > In case you have an hybrid situation with 3.11.3 , 3.11.4 and 3.11.5 that >> it is working and it is in production what do you recommend? > > > You shouldn't end up in this mixed-version sit

Re: [EXTERNAL] Cassandra 3.11.X upgrades

> > In case you have an hybrid situation with 3.11.3 , 3.11.4 and 3.11.5 that > it is working and it is in production what do you recommend? You shouldn't end up in this mixed-version situation at all. I would highly recommend you upgrade all the nodes to 3.11.5 or whatever the latest version is

Re: [EXTERNAL] Cassandra 3.11.X upgrades

Thanks everyone! In case you have an hybrid situation with 3.11.3 , 3.11.4 and 3.11.5 that it is working and it is in production what do you recommend? On Wed, Feb 12, 2020, 5:55 PM Erick Ramirez wrote: > So unless the sstable format has not been changed I can avoid to do that. > > > Just to

Re: [EXTERNAL] Cassandra 3.11.X upgrades

> > So unless the sstable format has not been changed I can avoid to do that. Just to reinforce what Jon and Sean already said, the above assumption is dangerous. It is always best to follow the recommended upgrade procedure and mixed-versions is never a good idea unless you've received instructi

RE: [EXTERNAL] Cassandra 3.11.X upgrades

Ah - I should have looked it up! Thank you for fixing my mistake. Sean Durity -Original Message- From: Michael Shuler Sent: Wednesday, February 12, 2020 3:17 PM To: user@cassandra.apache.org Subject: Re: [EXTERNAL] Cassandra 3.11.X upgrades On 2/12/20 12:58 PM, Durity, Sean R wrote

Re: [EXTERNAL] Cassandra 3.11.X upgrades

e.org" Subject: Re: [EXTERNAL] Cassandra 3.11.X upgrades Message from External Sender Thanks, everyone! @Jon https://lists.apache.org/thread.html/rd18814bfba487824ca95a58191f4dcdb86f15c9bb66cf2bcc29ddf0b%40%3Cuser.cassandra.apache.org%3E<https://urldefense.proofp

Re: [EXTERNAL] Cassandra 3.11.X upgrades

On 2/12/20 12:58 PM, Durity, Sean R wrote: Check the readme.txt for any upgrade notes Just a quick correction: NEWS.txt (upgrade (and other important) notes) CHANGES.txt (changelog with JIRAs) This is why we list links to these two files in the release announcements. -- Kind regards, Michael

Re: [EXTERNAL] Cassandra 3.11.X upgrades

Thanks, everyone! @Jon https://lists.apache.org/thread.html/rd18814bfba487824ca95a58191f4dcdb86f15c9bb66cf2bcc29ddf0b%40%3Cuser.cassandra.apache.org%3E I have a side response to something that looks to be controversial with the response from Anthony. So is it safe to go to production in a 1TB clus

RE: [EXTERNAL] Cassandra 3.11.X upgrades

>>A while ago, on my first cluster Understatement used so effectively. Jon is a master. On Wed, Feb 12, 2020 at 11:02 AM Sergio mailto:lapostadiser...@gmail.com>> wrote: Thanks for your reply! So unless the sstable format has not been changed I can avoid to do that. Correct? Best, Sergio

Re: [EXTERNAL] Cassandra 3.11.X upgrades

A while ago, on my first cluster, I decided to do an upgrade by adding nodes running 1.2 to an existing cluster running version 1.1. This was a bad decision, and at that point I decided to always play it safe and always stick to a single version, and never bootstrap in a node running different ver

Re: [EXTERNAL] Cassandra 3.11.X upgrades

Thanks for your reply! So unless the sstable format has not been changed I can avoid to do that. Correct? Best, Sergio On Wed, Feb 12, 2020, 10:58 AM Durity, Sean R wrote: > Check the readme.txt for any upgrade notes, but the basic procedure is to: > >- Verify that nodetool upgradesstabl

RE: [EXTERNAL] Cassandra 3.11.X upgrades

Check the readme.txt for any upgrade notes, but the basic procedure is to: * Verify that nodetool upgradesstables has completed successfully on all nodes from any previous upgrade * Turn off repairs and any other streaming operations (add/remove nodes) * Stop an un-upgraded node (seed