Thanks for the answers Paulo and Bowen.

Regards
Manish

On Thu, Oct 3, 2024 at 8:24 PM Bowen Song via user <
user@cassandra.apache.org> wrote:

> The supported and recommend route for upgrading 3.x to 5.x is to upgrade
> from 3.x to 4.x first, and then from 4.x to 5.x.
>
> Even if you've tested upgrading from 3.x to 5.x directly and it worked in
> a test environment, it is still unsupported and not recommended. That's
> because you may overlook some hidden issues which can bite you later.
>
> Please follow the tested and proven upgrade route if your data is valuable.
> On 03/10/2024 08:30, manish khandelwal wrote:
>
> Hi All
>
> We were evaluating the upgrades of Cassandra clusters managed by us to
> Cassandra 5.0. It's clear that Cassandra 4.0 to Cassandra 5.0 is supported.
> But I am not sure what is the status with respect to upgrading Cassandra
> 3.x to Cassandra 5.0.
>
> Some online resources I found say it is not possible and you should first
> jump to Cassandra 4.x. Following resources talk about the upgrade path
>
> 1.
> https://planetcassandra.org/news/top-5-questions-we-re-asked-about-apache-cassandra-r-5-0/
> 2.
> https://www.instaclustr.com/blog/top-5-questions-were-asked-about-apache-cassandra-5-0/
>
> Also Cassandra 5.0 announcement says, "Upgrading from 4.x to 5.0 has been
> designed and tested as an online upgrade, minimizing downtime for your
> applications." Here is the link
> <https://cassandra.apache.org/_/blog/Apache-Cassandra-5.0-Announcement.html>
> .
>
> Meanwhile there is a slack discussion
> <https://the-asf.slack.com/archives/CJZLTM05A/p1726630791029329> based on
> which my understanding is that there should not be an issue for upgrading
> to Cassandra 5.0 from Cassandra 3.x.
>
> I tried upgrading path (3.11.12- -> 5.0.0) using ccm but ccm seems to not
> allow me to change the JAVA version on one node and is picking the
> JAVA_HOME set on the machine.
>
> It would be of great help if somebody could confirm if Cassandra upgrade
> from 3.11.x to 5.0.0 is supported or not?
>
> Regards
> Manish
>
>

Reply via email to