[ 
https://issues.apache.org/jira/browse/CASSANDRA-18169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17677791#comment-17677791
 ] 

Alberto Bortolan commented on CASSANDRA-18169:
----------------------------------------------

>From what I could see, this particular behaviour, is specific for 
>{{{}system.local{}}}.
It can be reproduced starting up a brand new 3.11.x with x >=11. There is no 
need to have a migration involved.
–
The reason appears to be that {{system.local}} is updated and flushed very 
early during the startup process before commitlog replay and before 
StorageService is fully initialized generating sstables with an empty hostID.
The hostID information would be picked up from StorageService but as it's not 
initialized yet it will return null. Then CommitLogReplayer finds those 
sstables out. 

 

> Warning at startup in 3.11.11 or above version of Cassandra
> -----------------------------------------------------------
>
>                 Key: CASSANDRA-18169
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18169
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Local/Commit Log
>            Reporter: Mohammad Aburadeh
>            Assignee: Jacek Lewandowski
>            Priority: Normal
>             Fix For: 3.11.x
>
>
> We are seeing the following warning in Cassandra 3.11.11/14 at startup : 
> {code:java}
> WARN  [main] 2022-12-27 16:41:28,016 CommitLogReplayer.java:253 - Origin of 2 
> sstables is unknown or doesn't match the local node; commitLogIntervals for 
> them were ignored
> DEBUG [main] 2022-12-27 16:41:28,016 CommitLogReplayer.java:254 - Ignored 
> commitLogIntervals from the following sstables: 
> [/data/cassandra/data/system/local-7ad54392bcdd35a684174e047860b377/me-65-big-Data.db,
>  
> /data/cassandra/data/system/local-7ad54392bcdd35a684174e047860b377/me-64-big-Data.db]
>  {code}
> It looks like HostID metadata is missing at startup in the system.local 
> table. 
> We noticed that this issue does not exist in the 4.0.X version of Cassandra. 
> Could you please fix it in 3.11.X Cassandra? 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to