You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Blake Eggleston (Jira)" <ji...@apache.org> on 2025/09/04 17:15:00 UTC

[jira] [Created] (CASSANDRA-20891) CEP-45: Node Replace

Blake Eggleston created CASSANDRA-20891:
-------------------------------------------

             Summary: CEP-45: Node Replace
                 Key: CASSANDRA-20891
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-20891
             Project: Apache Cassandra
          Issue Type: Improvement
          Components: Consistency/Streaming
            Reporter: Blake Eggleston


Host replacement is the simplest topology change to make since there is token movement. Contrary to the initial design, topology changes shouldn't need the bulk transfer mechanism. SSTables streamed in will either be fully reconciled, or contain an sstable component describing which ids they contain. We can populate the new node's view of mutations it has witnessed from this (and the writes it receives during it's time in a pending state). Fully reconciled should be discovered via offsets broadcasting, and this should put the node in the right state to start handling reads once streaming completes.

Main changes are:
 * Streaming path
 ** Need to add sstable offsets to mutation tracking service as replicated.
 * Read path
 ** Pull mutation rejection
 *** Since we'll be advertising offsets that we only have in sstable form, we will have to reject some mutation pull requests. This will need to be gracefully handled by read coordinator
 ** Durability update
 *** Node needs to know which mutations it has in sstables and/or are fully reconciled even without log entries across restarts



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

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