You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (Jira)" <ji...@apache.org> on 2026/07/10 15:31:00 UTC

[jira] [Created] (CASSANDRA-21496) RemoveNodeStreams and ReconfigureCMS RESTORE_REPLICA_COUNT streams received by replicas are mis-parsed as OTHER.

Aleksey Yeschenko created CASSANDRA-21496:
---------------------------------------------

             Summary: RemoveNodeStreams and ReconfigureCMS RESTORE_REPLICA_COUNT streams received by replicas are mis-parsed as OTHER.
                 Key: CASSANDRA-21496
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21496
             Project: Apache Cassandra
          Issue Type: Bug
            Reporter: Aleksey Yeschenko


{{RemoveNodeStreams#startStreaming()}} and {{ReconfigureCMS#streamRanges()}} build an {{INITIATE_DATA_MOVEMENTS_REQ}} payload
whose {{streamOperation}} field is set to {{StreamOperation.RESTORE_REPLICA_COUNT.name()}}, i.e. the enum constant name {{RESTORE_REPLICA_COUNT}}.

{{DataMovementVerbHandler#doVerb()}} on the receiver parses that string with {{StreamOperation.fromString(message.payload.streamOperation))}},
incorrectly getting {{StreamOperation.OTHER}} (since {{"RESTORE_REPLICA_COUNT" != "Restore replica count"}}).

Current impact: this causes MVs to require rebuild unnecessarily on removenode.
Future impact: this affects CEP-45 topology change logic. I have a temporary workaround there but it's inelegant.



--
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