Re: SSTable Migration to oa-* Format After Upgrade to 5

[Luciano Greiner]

Thank you Paul!

So should I restart the nodes with UPGRADING mode and run the
upgradesstables again?

Thank you!

Luciano Greiner
(54) 996309845

On Sun, Mar 16, 2025 at 2:58 AM Paul Chandler  wrote:
>
> Hi Luciano,
>
> It sounds like you could have the storage_compatibility_mode set to the 
> default CASSANDRA_4 value, check this and change it to UPGRADING or NONE.
>
> Full details can be found in the Cassandra.yaml 
> https://cassandra.apache.org/doc/latest/cassandra/managing/configuration/cass_yaml_file.html#storage_compatibility_mode
>
> Regards
>
> Paul
>
> Sent from my iPhone
>
> On 16 Mar 2025, at 07:48, Luciano Greiner  wrote:
>
> Hi,
>
> We recently upgraded our clusters from 4.1.5 to 5.0.3 and now I’m
> trying to migrate SSTable files to the new oa-* format, but it’s not
> working as I expected.
>
> What I Tried:
>
> nodetool flush + upgradesstables → Completed quickly with success
> messages, but no SSTables were rewritten.
> nodetool upgradesstables -a → Triggered compactions, but new SSTables
> are still in the old nb-* format.
>
> What’s the recommended approach to ensure SSTables migrate to oa-*? Is
> it really necessary?
>
> Thanks!
>
> Luciano

Re: SSTable Migration to oa-* Format After Upgrade to 5

[Paul Chandler]

Yes, that should sort it out.

Regards 

Paul
Sent from my iPhone

> On 16 Mar 2025, at 18:34, Luciano Greiner  wrote:
> 
> Thank you Paul!
> 
> So should I restart the nodes with UPGRADING mode and run the
> upgradesstables again?
> 
> Thank you!
> 
> Luciano Greiner
> (54) 996309845
> 
>> On Sun, Mar 16, 2025 at 2:58 AM Paul Chandler  wrote:
>> 
>> Hi Luciano,
>> 
>> It sounds like you could have the storage_compatibility_mode set to the 
>> default CASSANDRA_4 value, check this and change it to UPGRADING or NONE.
>> 
>> Full details can be found in the Cassandra.yaml 
>> https://cassandra.apache.org/doc/latest/cassandra/managing/configuration/cass_yaml_file.html#storage_compatibility_mode
>> 
>> Regards
>> 
>> Paul
>> 
>> Sent from my iPhone
>> 
>> On 16 Mar 2025, at 07:48, Luciano Greiner  wrote:
>> 
>> Hi,
>> 
>> We recently upgraded our clusters from 4.1.5 to 5.0.3 and now I’m
>> trying to migrate SSTable files to the new oa-* format, but it’s not
>> working as I expected.
>> 
>> What I Tried:
>> 
>> nodetool flush + upgradesstables → Completed quickly with success
>> messages, but no SSTables were rewritten.
>> nodetool upgradesstables -a → Triggered compactions, but new SSTables
>> are still in the old nb-* format.
>> 
>> What’s the recommended approach to ensure SSTables migrate to oa-*? Is
>> it really necessary?
>> 
>> Thanks!
>> 
>> Luciano

Re: SSTable Migration to oa-* Format After Upgrade to 5

[edi mari]

Sorry for jumping into the conversation, but I wanted to ask— is there an
guide for upgrading Cassandra from v4 to v5?

Edi

בתאריך יום א׳, 16 במרץ 2025, 19:33, מאת Paul Chandler ‏:

> Yes, that should sort it out.
>
> Regards
>
> Paul
> Sent from my iPhone
>
> > On 16 Mar 2025, at 18:34, Luciano Greiner 
> wrote:
> >
> > Thank you Paul!
> >
> > So should I restart the nodes with UPGRADING mode and run the
> > upgradesstables again?
> >
> > Thank you!
> >
> > Luciano Greiner
> > (54) 996309845
> >
> >> On Sun, Mar 16, 2025 at 2:58 AM Paul Chandler 
> wrote:
> >>
> >> Hi Luciano,
> >>
> >> It sounds like you could have the storage_compatibility_mode set to the
> default CASSANDRA_4 value, check this and change it to UPGRADING or NONE.
> >>
> >> Full details can be found in the Cassandra.yaml
> https://cassandra.apache.org/doc/latest/cassandra/managing/configuration/cass_yaml_file.html#storage_compatibility_mode
> >>
> >> Regards
> >>
> >> Paul
> >>
> >> Sent from my iPhone
> >>
> >> On 16 Mar 2025, at 07:48, Luciano Greiner 
> wrote:
> >>
> >> Hi,
> >>
> >> We recently upgraded our clusters from 4.1.5 to 5.0.3 and now I’m
> >> trying to migrate SSTable files to the new oa-* format, but it’s not
> >> working as I expected.
> >>
> >> What I Tried:
> >>
> >> nodetool flush + upgradesstables → Completed quickly with success
> >> messages, but no SSTables were rewritten.
> >> nodetool upgradesstables -a → Triggered compactions, but new SSTables
> >> are still in the old nb-* format.
> >>
> >> What’s the recommended approach to ensure SSTables migrate to oa-*? Is
> >> it really necessary?
> >>
> >> Thanks!
> >>
> >> Luciano
>
>

Re: SSTable Migration to oa-* Format After Upgrade to 5

[edi mari]

Great ,Thanks Scott .

בתאריך יום א׳, 16 במרץ 2025, 21:40, מאת C. Scott Andreas ‏<
sc...@paradoxica.net>:

> Hi Edi,
>
> Details are in NEWS.txt:
> https://github.com/apache/cassandra/blob/cassandra-5.0/NEWS.txt
>
> – Scott
>
> On Mar 16, 2025, at 11:37 AM, edi mari  wrote:
>
> 
>
> Sorry for jumping into the conversation, but I wanted to ask— is there an
> guide for upgrading Cassandra from v4 to v5?
>
> Edi
>
> בתאריך יום א׳, 16 במרץ 2025, 19:33, מאת Paul Chandler ‏ >:
>
>> Yes, that should sort it out.
>>
>> Regards
>>
>> Paul
>> Sent from my iPhone
>>
>> > On 16 Mar 2025, at 18:34, Luciano Greiner 
>> wrote:
>> >
>> > Thank you Paul!
>> >
>> > So should I restart the nodes with UPGRADING mode and run the
>> > upgradesstables again?
>> >
>> > Thank you!
>> >
>> > Luciano Greiner
>> > (54) 996309845
>> >
>> >> On Sun, Mar 16, 2025 at 2:58 AM Paul Chandler 
>> wrote:
>> >>
>> >> Hi Luciano,
>> >>
>> >> It sounds like you could have the storage_compatibility_mode set to
>> the default CASSANDRA_4 value, check this and change it to UPGRADING or
>> NONE.
>> >>
>> >> Full details can be found in the Cassandra.yaml
>> https://cassandra.apache.org/doc/latest/cassandra/managing/configuration/cass_yaml_file.html#storage_compatibility_mode
>> >>
>> >> Regards
>> >>
>> >> Paul
>> >>
>> >> Sent from my iPhone
>> >>
>> >> On 16 Mar 2025, at 07:48, Luciano Greiner 
>> wrote:
>> >>
>> >> Hi,
>> >>
>> >> We recently upgraded our clusters from 4.1.5 to 5.0.3 and now I’m
>> >> trying to migrate SSTable files to the new oa-* format, but it’s not
>> >> working as I expected.
>> >>
>> >> What I Tried:
>> >>
>> >> nodetool flush + upgradesstables → Completed quickly with success
>> >> messages, but no SSTables were rewritten.
>> >> nodetool upgradesstables -a → Triggered compactions, but new SSTables
>> >> are still in the old nb-* format.
>> >>
>> >> What’s the recommended approach to ensure SSTables migrate to oa-*? Is
>> >> it really necessary?
>> >>
>> >> Thanks!
>> >>
>> >> Luciano
>>
>>

Re: SSTable Migration to oa-* Format After Upgrade to 5

[C. Scott Andreas]

Hi Edi,Details are in NEWS.txt: https://github.com/apache/cassandra/blob/cassandra-5.0/NEWS.txt– ScottOn Mar 16, 2025, at 11:37 AM, edi mari  wrote:Sorry for jumping into the conversation, but I wanted to ask— is there an guide for upgrading Cassandra from v4 to v5?
Edi
בתאריך יום א׳, 16 במרץ 2025, 19:33, מאת Paul Chandler ‏:Yes, that should sort it out.

Regards 

Paul
Sent from my iPhone

> On 16 Mar 2025, at 18:34, Luciano Greiner  wrote:
> 
> Thank you Paul!
> 
> So should I restart the nodes with UPGRADING mode and run the
> upgradesstables again?
> 
> Thank you!
> 
> Luciano Greiner
> (54) 996309845
> 
>> On Sun, Mar 16, 2025 at 2:58 AM Paul Chandler  wrote:
>> 
>> Hi Luciano,
>> 
>> It sounds like you could have the storage_compatibility_mode set to the default CASSANDRA_4 value, check this and change it to UPGRADING or NONE.
>> 
>> Full details can be found in the Cassandra.yaml https://cassandra.apache.org/doc/latest/cassandra/managing/configuration/cass_yaml_file.html#storage_compatibility_mode
>> 
>> Regards
>> 
>> Paul
>> 
>> Sent from my iPhone
>> 
>> On 16 Mar 2025, at 07:48, Luciano Greiner  wrote:
>> 
>> Hi,
>> 
>> We recently upgraded our clusters from 4.1.5 to 5.0.3 and now I’m
>> trying to migrate SSTable files to the new oa-* format, but it’s not
>> working as I expected.
>> 
>> What I Tried:
>> 
>> nodetool flush + upgradesstables → Completed quickly with success
>> messages, but no SSTables were rewritten.
>> nodetool upgradesstables -a → Triggered compactions, but new SSTables
>> are still in the old nb-* format.
>> 
>> What’s the recommended approach to ensure SSTables migrate to oa-*? Is
>> it really necessary?
>> 
>> Thanks!
>> 
>> Luciano