Re: Upgrade 3.11.6 to 4.0.3, commitlog warns

2022-05-13 Thread Erick Ramirez
>
> 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

2022-05-13 Thread Sebastian Albrecht
Am Fr., 13. Mai 2022 um 12:05 Uhr schrieb Erick Ramirez <
erickramire...@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

2022-05-13 Thread Erick Ramirez
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!

>