You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Josh McKenzie (Jira)" <ji...@apache.org> on 2022/05/11 20:18:00 UTC

[jira] [Updated] (CASSANDRA-17525) Local host-id may not be set when replaying commit log

     [ https://issues.apache.org/jira/browse/CASSANDRA-17525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh McKenzie updated CASSANDRA-17525:
--------------------------------------
    Fix Version/s: 4.1-rc
                       (was: 4.1)

> Local host-id may not be set when replaying commit log
> ------------------------------------------------------
>
>                 Key: CASSANDRA-17525
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17525
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Local/Commit Log
>            Reporter: Jon Meredith
>            Assignee: Jon Meredith
>            Priority: Normal
>             Fix For: 4.0.x, 4.1-rc
>
>
> The local host id is now used when replaying commit logs to prevent data loss when moving SSTables between nodes (CASSANDRA-16619).
> The local host-id is assigned once on initial startup and persisted to the local.local table for use on subsequent startups - however it remains in the memtable/commitlog until the local table is eventually flushed.
> If the node dies for any reason before the flush takes place, on the next restart a new host id will be allocated before the commit log is replayed and any sstables appearing in the commit log will be skipped incorrectly.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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