[
https://issues.apache.org/jira/browse/CASSANDRA-19297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Eggleston updated CASSANDRA-19297:
----------------------------------------
Test and Documentation Plan: ci
Status: Patch Available (was: Open)
A bootstrapping node missing it's own exclusive sync point wouldn't be a
problem since bootstrap won't proceed until the sync point is acked by at least
a quorum. Even if a node misses a sync point txn and has out of date reject
before values, the other nodes will reject any txnids that should be rejected.
I've pushed up 2 tests checking this here:
[https://github.com/apache/cassandra-accord/pull/104]
> Accord: RejectBefore must be up-to-date on joining nodes before ready to
> coordinate
> -----------------------------------------------------------------------------------
>
> Key: CASSANDRA-19297
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19297
> Project: Cassandra
> Issue Type: Improvement
> Components: Accord
> Reporter: Benedict Elliott Smith
> Assignee: Blake Eggleston
> Priority: Normal
> Labels: pull-request-available
>
> The exclusive sync point used to join the shard will be known by a majority
> of the existing replicas, but in the event the quorum changes and the new
> replica has not recorded the exclusive sync point this might in principle
> lead to failing to reject a TxnId that should be rejected.
> Simple fix, but introduce tests to corroborate this issue, and see if can
> reproduce in burn test.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
