[
https://issues.apache.org/jira/browse/CASSANDRA-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17030054#comment-17030054
]
Sam Tunnicliffe commented on CASSANDRA-14740:
---------------------------------------------
Sorry, this broke {{MessageForwardingTest}} by forcing the RF of the test
keyspace to 3; I mistakenly thought that test was already failing before.
Fixed in a follow up commit
[{{cb4314ee96}}|https://github.com/apache/cassandra/commit/cb4314ee96922f870f5b30d6594a42d2007a5bb2]
with CI runs for
[jdk8|https://circleci.com/workflow-run/3e9a34a0-a6b7-4b41-9e7f-667233f858c6]
and
[jdk11|https://circleci.com/workflow-run/442cd66f-25c4-4d39-988b-7bdd3aceae5a]
> BlockingReadRepair does not maintain monotonicity during range movements
> ------------------------------------------------------------------------
>
> Key: CASSANDRA-14740
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14740
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Coordination
> Reporter: Benedict Elliott Smith
> Assignee: Benedict Elliott Smith
> Priority: Urgent
> Labels: correctness
> Fix For: 4.0, 4.0-alpha
>
>
> The BlockingReadRepair code introduced by CASSANDRA-10726 requires that each
> of the queried nodes are written to, but pending nodes are not considered.
> If there is a pending range movement, one of these writes may be ‘lost’ when
> the range movement completes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
