Upgrade 3.11.6 to 4.0.3, commitlog warns

[Sebastian Albrecht <se...@agido.com>]

Hi,
i just upgraded my one-node cassandra from 3.11.6 to 4.0.3. Now every time
it starts it's producing the following warn messages in the log like:
WARN [main] 2022-01-18 10:55:00,696 CommitLogReplayer.java:305 - Origin of
2 sstables is unknown or doesn't match the local node; commitLogIntervals
for them were ignored

It looks like the data is still consistent but i am not sure if i should
worry. I know there is the sstableupgrade tool where all SSTable files can
be upgraded but i want to be sure all is ok in the time i did not run it on
all keyspaces. Previous upgrades did not produce those warnings.
Even automatically upgraded tables like system.compaction_history (sstable
files all have the current name prefix 'nb') are shown in the warning
messages.

Appreciate all helps,
Sebastian.

Re: Upgrade 3.11.6 to 4.0.3, commitlog warns

[Erick Ramirez <er...@apache.org>]

>
> Thank you for that clarification, Erick. So do i understand correctly,
> that because of the upgrade the host id changed and therefore differs from
> the ones in the sstables where the old host id is still sitting until a
> sstable upgrade?
>

Not quite. :) The host ID will never change for the lifetime of a node. As
I said:

... the SSTables now contain the host ID on which they were created ...


the implication being that the older versions didn't store the host ID with
the SSTables hence leading to the "origin unknown" warning in newer
versions. Cheers!

Re: Upgrade 3.11.6 to 4.0.3, commitlog warns

[Sebastian Albrecht <se...@agido.com>]

Am Fr., 13. Mai 2022 um 12:05 Uhr schrieb Erick Ramirez <
erickramirezau@apache.org>:

> It's expected and is nothing to worry about. From C* 3.0.25/3.11.11/4.0,
> the SSTables now contain the host ID on which they were created to prevent
> loss of commitlog data when SSTables are moved/copied to other nodes
> (CASSANDRA-16619). That's why the message is logged at WARN level instead
> of ERROR. Cheers!
>

Thank you for that clarification, Erick. So do i understand correctly, that
because of the upgrade the host id changed and therefore differs from the
ones in the sstables where the old host id is still sitting until a sstable
upgrade?

Thx,
Sebastian.

Re: Upgrade 3.11.6 to 4.0.3, commitlog warns

[Erick Ramirez <er...@apache.org>]

It's expected and is nothing to worry about. From C* 3.0.25/3.11.11/4.0,
the SSTables now contain the host ID on which they were created to prevent
loss of commitlog data when SSTables are moved/copied to other nodes
(CASSANDRA-16619). That's why the message is logged at WARN level instead
of ERROR. Cheers!

>