[
https://issues.apache.org/jira/browse/CASSANDRA-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-14740:
----------------------------------------
Fix Version/s: (was: 4.0-beta)
4.0-alpha
Since Version: 4.0-alpha
Source Control Link:
https://github.com/apache/cassandra/commit/0f22dab1a015cb84d9857f940de5a256bfbee083
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed to trunk in {{0f22dab1a015cb84d9857f940de5a256bfbee083}}. Final CI
run after rebasing with only previously known failures:
[jdk8|https://circleci.com/workflow-run/3cb3c20e-6dea-4fd6-8aff-193e1e7d298b] &;
[jdk11|https://circleci.com/workflow-run/024ba3cd-c112-4f73-a562-b364ea420e3c]
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
