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

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Duplicate
• Fix Version/s: 4.0.x, 4.1.x
• Component/s: Local/Commit Log
• Bug Category: Correctness - Recoverable Corruption / Loss
• Severity: Low
• Complexity: Normal
• Discovered By: DTest
• Platform: All
• Assignee: Jon Meredith
• Reporter: Jon Meredith

Authors

Jon Meredith

• Created: 05/Apr/22 20:38
• Updated: 12/Apr/23 16:10
• Resolved: 12/Apr/23 16:10

Description

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.

Issue Links

• Blocked: CASSANDRA-18153 Memtable being flushed without hostId in version "me" and newer during CommitLogReplay