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

C. Scott Andreas commented on CASSANDRA-13704:
----------------------------------------------

Hi Mick, I don’t think that’s an appropriate way to frame this change. What are 
the scenarios not covered that you envision?

This fix prevents nodes from rejecting read and write requests that are known 
to have been directed to the improper replica. Every single one of them 
rejected indicates that the user has been guarded against inconsistent reads, 
missing data on read, or permanent and unrecoverable data loss on write. 
Further, there is no availability to be “gained” by responding to a read or a 
write request from the wrong place - it’s like reading or writing to /dev/null.

Prior to TCM, there are zero circumstances I would run Apache Cassandra without 
this guard enabled.

> Safer handling of out of range tokens
> -------------------------------------
>
>                 Key: CASSANDRA-13704
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13704
>             Project: Apache Cassandra
>          Issue Type: Bug
>          Components: Legacy/Coordination, Legacy/Observability
>            Reporter: Sam Tunnicliffe
>            Assignee: Caleb Rackliffe
>            Priority: Urgent
>             Fix For: 4.0.14, 4.1.7, 5.0.1
>
>         Attachments: CASSANDRA-13704_5-0_23_ci_summary.html, 
> CASSANDRA-13704_5-0_23_results_details.tar.xz, 
> CASSANDRA-13704_5-0_24_ci_summary.html, 
> CASSANDRA-13704_5-0_24_results_details.tar.xz, 
> CASSANDRA-13704_5-0_25_ci_summary.html, 
> CASSANDRA-13704_5-0_25_results_details.tar.xz, ci_summary-1.html, 
> ci_summary-2.html, ci_summary.html, result_details.tar-1.gz, 
> result_details.tar-2.gz, result_details.tar.gz
>
>          Time Spent: 8h 10m
>  Remaining Estimate: 0h
>
> It is possible for nodes to have a divergent view of the ring, which can 
> result in some operations being sent to the wrong nodes. This is an umbrella 
> ticket to mitigate such issues by adding logging when a node is asked to 
> perform an operation for tokens it does not own. This will be useful for 
> detecting when the nodes' views of the ring diverge, which is not highly 
> visible at the moment, and also for post-hoc analysis.
> It may also be beneficial to straight up reject certain operations, though 
> this will need to balance the risk of performing those ops against the 
> consequences rejecting them has on availability.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to