You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Runtian Liu <cu...@gmail.com> on 2022/06/14 05:17:04 UTC
Cassandra 3.0 upgrade
Hi,
I am running Cassandra version 3.0.14 at scale on thousands of nodes. I am
planning to do a minor version upgrade from 3.0.14 to 3.0.26 in a safe
manner. My eventual goal is to upgrade from 3.0.26 to a major release 4.0.
As you know, there are multiple minor releases between 3.0.14 and 3.0.26,
so I am planning to upgrade in 2-3 batches say 1) 3.0.14 → 3.0.16 2) 3.0.16
to 3.0.20 3) 3.0.20 → 3.0.26.
. Do you have suggestions or anything that I need to be aware of? Is there
any minor release between 3.0.14 and 3.0.26, which is not safe etc.?
Best regards.
Re: Cassandra 3.0 upgrade
Posted by Jaydeep Chovatia <ch...@gmail.com>.
Yeah, we have a fork of Cassandra with custom patches, and a fork of dtest
with some additional custom tests, so we will have to upgrade dtest as
well.
Is there any specific tag of dtest we should use or the latest trunk is
fine to test against 3.0.27?
Jaydeep
On Mon, Jun 13, 2022 at 10:51 PM C. Scott Andreas <sc...@paradoxica.net>
wrote:
> If you have a fork of Cassandra with custom patches and build/execute the
> dtest suite as part of qualification, you’d want to upgrade that as well.
>
> Note that in more recent 3.0.x releases, the project also introduced
> in-JVM dtests. This is a new suite that serves a similar purpose to the
> Python dtests, but which are much more reliable and allow for spawning of
> multiple C* instances in a JVM for testing. I’d recommend adding this to
> your build/CI process if so.
>
> If you don’t have a fork and deploy stock builds of Cassandra, you
> probably don’t need to worry about the dtest repo.
>
> - Scott
>
> On Jun 13, 2022, at 10:36 PM, Jaydeep Chovatia <ch...@gmail.com>
> wrote:
>
>
> Thanks Jeff and Scott for valuable feedback!
> One more question, do we have to upgrade the dTest repo if we go to
> 3.0.27, or the one we have currently already working with 3.0.14 should
> continue to work fine?
>
> Jaydeep
>
> On Mon, Jun 13, 2022 at 10:25 PM C. Scott Andreas <sc...@paradoxica.net>
> wrote:
>
>> Thank you for reaching out, and for planning the upgrade!
>>
>> Upgrading from 3.0.14 to 3.0.27 would be best, followed by upgrading to
>> 4.0.4.
>>
>> 3.0.14 contains a number of serious bugs that are resolved in more recent
>> 3.0.x releases (3.0.19+ are generally good/safe). Upgrading to 3.0.27 will
>> put you on a great 3.0.x build. If all looks good from there, you should
>> have an easy upgrade to 4.0.4.
>>
>> I would not recommend passing through intermediate 3.0.x releases on the
>> way to 3.0.27; doing so is not necessary.
>>
>> Cheers,
>>
>> - Scott
>>
>>
>> On Jun 13, 2022, at 10:17 PM, Runtian Liu <cu...@gmail.com> wrote:
>>
>>
>>
>> Hi,
>>
>> I am running Cassandra version 3.0.14 at scale on thousands of nodes. I
>> am planning to do a minor version upgrade from 3.0.14 to 3.0.26 in a safe
>> manner. My eventual goal is to upgrade from 3.0.26 to a major release 4.0.
>>
>> As you know, there are multiple minor releases between 3.0.14 and 3.0.26,
>> so I am planning to upgrade in 2-3 batches say 1) 3.0.14 → 3.0.16 2) 3.0.16
>> to 3.0.20 3) 3.0.20 → 3.0.26.
>>
>> . Do you have suggestions or anything that I need to be aware of? Is
>> there any minor release between 3.0.14 and 3.0.26, which is not safe etc.?
>>
>> Best regards.
>>
>>
Re: Cassandra 3.0 upgrade
Posted by "C. Scott Andreas" <sc...@paradoxica.net>.
If you have a fork of Cassandra with custom patches and build/execute the dtest suite as part of qualification, you’d want to upgrade that as well.
Note that in more recent 3.0.x releases, the project also introduced in-JVM dtests. This is a new suite that serves a similar purpose to the Python dtests, but which are much more reliable and allow for spawning of multiple C* instances in a JVM for testing. I’d recommend adding this to your build/CI process if so.
If you don’t have a fork and deploy stock builds of Cassandra, you probably don’t need to worry about the dtest repo.
- Scott
> On Jun 13, 2022, at 10:36 PM, Jaydeep Chovatia <ch...@gmail.com> wrote:
>
>
> Thanks Jeff and Scott for valuable feedback!
> One more question, do we have to upgrade the dTest repo if we go to 3.0.27, or the one we have currently already working with 3.0.14 should continue to work fine?
>
> Jaydeep
>
>> On Mon, Jun 13, 2022 at 10:25 PM C. Scott Andreas <sc...@paradoxica.net> wrote:
>> Thank you for reaching out, and for planning the upgrade!
>>
>> Upgrading from 3.0.14 to 3.0.27 would be best, followed by upgrading to 4.0.4.
>>
>> 3.0.14 contains a number of serious bugs that are resolved in more recent 3.0.x releases (3.0.19+ are generally good/safe). Upgrading to 3.0.27 will put you on a great 3.0.x build. If all looks good from there, you should have an easy upgrade to 4.0.4.
>>
>> I would not recommend passing through intermediate 3.0.x releases on the way to 3.0.27; doing so is not necessary.
>>
>> Cheers,
>>
>> - Scott
>>
>>
>>>> On Jun 13, 2022, at 10:17 PM, Runtian Liu <cu...@gmail.com> wrote:
>>>>
>>>
>>> Hi,
>>>
>>> I am running Cassandra version 3.0.14 at scale on thousands of nodes. I am planning to do a minor version upgrade from 3.0.14 to 3.0.26 in a safe manner. My eventual goal is to upgrade from 3.0.26 to a major release 4.0.
>>>
>>> As you know, there are multiple minor releases between 3.0.14 and 3.0.26, so I am planning to upgrade in 2-3 batches say 1) 3.0.14 → 3.0.16 2) 3.0.16 to 3.0.20 3) 3.0.20 → 3.0.26.
>>> . Do you have suggestions or anything that I need to be aware of? Is there any minor release between 3.0.14 and 3.0.26, which is not safe etc.?
>>>
>>> Best regards.
>>>
Re: Cassandra 3.0 upgrade
Posted by Jaydeep Chovatia <ch...@gmail.com>.
Thanks Jeff and Scott for valuable feedback!
One more question, do we have to upgrade the dTest repo if we go to 3.0.27,
or the one we have currently already working with 3.0.14 should continue to
work fine?
Jaydeep
On Mon, Jun 13, 2022 at 10:25 PM C. Scott Andreas <sc...@paradoxica.net>
wrote:
> Thank you for reaching out, and for planning the upgrade!
>
> Upgrading from 3.0.14 to 3.0.27 would be best, followed by upgrading to
> 4.0.4.
>
> 3.0.14 contains a number of serious bugs that are resolved in more recent
> 3.0.x releases (3.0.19+ are generally good/safe). Upgrading to 3.0.27 will
> put you on a great 3.0.x build. If all looks good from there, you should
> have an easy upgrade to 4.0.4.
>
> I would not recommend passing through intermediate 3.0.x releases on the
> way to 3.0.27; doing so is not necessary.
>
> Cheers,
>
> - Scott
>
>
> On Jun 13, 2022, at 10:17 PM, Runtian Liu <cu...@gmail.com> wrote:
>
>
>
> Hi,
>
> I am running Cassandra version 3.0.14 at scale on thousands of nodes. I am
> planning to do a minor version upgrade from 3.0.14 to 3.0.26 in a safe
> manner. My eventual goal is to upgrade from 3.0.26 to a major release 4.0.
>
> As you know, there are multiple minor releases between 3.0.14 and 3.0.26,
> so I am planning to upgrade in 2-3 batches say 1) 3.0.14 → 3.0.16 2) 3.0.16
> to 3.0.20 3) 3.0.20 → 3.0.26.
>
> . Do you have suggestions or anything that I need to be aware of? Is there
> any minor release between 3.0.14 and 3.0.26, which is not safe etc.?
>
> Best regards.
>
>
Re: Cassandra 3.0 upgrade
Posted by "C. Scott Andreas" <sc...@paradoxica.net>.
Thank you for reaching out, and for planning the upgrade!
Upgrading from 3.0.14 to 3.0.27 would be best, followed by upgrading to 4.0.4.
3.0.14 contains a number of serious bugs that are resolved in more recent 3.0.x releases (3.0.19+ are generally good/safe). Upgrading to 3.0.27 will put you on a great 3.0.x build. If all looks good from there, you should have an easy upgrade to 4.0.4.
I would not recommend passing through intermediate 3.0.x releases on the way to 3.0.27; doing so is not necessary.
Cheers,
- Scott
> On Jun 13, 2022, at 10:17 PM, Runtian Liu <cu...@gmail.com> wrote:
>
>
> Hi,
>
> I am running Cassandra version 3.0.14 at scale on thousands of nodes. I am planning to do a minor version upgrade from 3.0.14 to 3.0.26 in a safe manner. My eventual goal is to upgrade from 3.0.26 to a major release 4.0.
>
> As you know, there are multiple minor releases between 3.0.14 and 3.0.26, so I am planning to upgrade in 2-3 batches say 1) 3.0.14 → 3.0.16 2) 3.0.16 to 3.0.20 3) 3.0.20 → 3.0.26.
> . Do you have suggestions or anything that I need to be aware of? Is there any minor release between 3.0.14 and 3.0.26, which is not safe etc.?
>
> Best regards.
>
Re: Cassandra 3.0 upgrade
Posted by Jeff Jirsa <jj...@gmail.com>.
The versions with caveats should all be enumerated in
https://github.com/apache/cassandra/blob/cassandra-3.0/NEWS.txt
The biggest caveat was 3.0.14 (which had the fix for cassandra-13004),
which you're already on.
Personally, I'd qualify exactly one upgrade, and rather than doing 3
different upgrades, just do exactly one and spend 3 times as long proving
it's safe in non-production.
On Mon, Jun 13, 2022 at 10:17 PM Runtian Liu <cu...@gmail.com> wrote:
> Hi,
>
> I am running Cassandra version 3.0.14 at scale on thousands of nodes. I am
> planning to do a minor version upgrade from 3.0.14 to 3.0.26 in a safe
> manner. My eventual goal is to upgrade from 3.0.26 to a major release 4.0.
>
> As you know, there are multiple minor releases between 3.0.14 and 3.0.26,
> so I am planning to upgrade in 2-3 batches say 1) 3.0.14 → 3.0.16 2) 3.0.16
> to 3.0.20 3) 3.0.20 → 3.0.26.
>
> . Do you have suggestions or anything that I need to be aware of? Is there
> any minor release between 3.0.14 and 3.0.26, which is not safe etc.?
>
> Best regards.
>
>