mes up clean (it will
>>>>function normally in the cluster – even with mixed versions)
>>>>- Repeat for all nodes
>>>>- Run upgradesstables on each node (as many at a time as your load
>>>>will allow). Minor upgrades usually don’t require this step (only if
: 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
>
> 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
ormally in the cluster – even with mixed versions)
>>>>- Repeat for all nodes
>>>>- Run upgradesstables on each node (as many at a time as your load
>>>>will allow). Minor upgrades usually don’t require this step (only if the
>>>>sstable
anged), but it is good to check.
>>>- NOTE: in most cases applications can keep running and will not
>>>notice much impact – unless the cluster is overloaded and a single node
>>>down causes impact.
>>>
>>>
>>>
>>>
&
down causes impact.
>>
>>
>>
>>
>>
>>
>>
>> Sean Durity – Staff Systems Engineer, Cassandra
>>
>>
>>
>> *From:* Sergio
>> *Sent:* Wednesday, February 12, 2020 11:36 AM
>> *To:* u
dra
>
>
>
> *From:* Sergio
> *Sent:* Wednesday, February 12, 2020 11:36 AM
> *To:* user@cassandra.apache.org
> *Subject:* [EXTERNAL] Cassandra 3.11.X upgrades
>
>
>
> Hi guys!
>
> How do you usually upgrade your cluster for minor version upgrades?
>
> I tri
+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
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. 😁
>
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
>
> 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
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
>
> 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
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
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
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
ut it is good to check.
>- NOTE: in most cases applications can keep running and will not
>notice much impact – unless the cluster is overloaded and a single node
>down causes impact.
>
>
>
>
>
>
>
> Sean Durity – Staff Systems Engineer, Cassandra
>
ssandra.apache.org>
Subject: [EXTERNAL] Cassandra 3.11.X upgrades
Hi guys!
How do you usually upgrade your cluster for minor version upgrades?
I tried to add a node with 3.11.5 version to a test cluster with 3.11.4 nodes.
Is there any restriction?
Best,
Sergio
___
cluster is overloaded and a single node
>>down causes impact.
>>
>>
>>
>>
>>
>>
>>
>> Sean Durity – Staff Systems Engineer, Cassandra
>>
>>
>>
>> *From:* Sergio
>> *Sent:* Wednesday, February 12, 2020 11:36 AM
>>
> Sean Durity – Staff Systems Engineer, Cassandra
>
>
>
> *From:* Sergio
> *Sent:* Wednesday, February 12, 2020 11:36 AM
> *To:* user@cassandra.apache.org
> *Subject:* [EXTERNAL] Cassandra 3.11.X upgrades
>
>
>
> Hi guys!
>
> How do you usually upgrade yo
.
Sean Durity – Staff Systems Engineer, Cassandra
From: Sergio
Sent: Wednesday, February 12, 2020 11:36 AM
To: user@cassandra.apache.org
Subject: [EXTERNAL] Cassandra 3.11.X upgrades
Hi guys!
How do you usually upgrade your cluster for minor version upgrades?
I tried to add a node with 3.11.5
Hi guys!
How do you usually upgrade your cluster for minor version upgrades?
I tried to add a node with 3.11.5 version to a test cluster with 3.11.4
nodes.
Is there any restriction?
Best,
Sergio
22 matches
Mail list logo
