This is an automated email from the ASF dual-hosted git repository.
samt pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git
The following commit(s) were added to refs/heads/trunk by this push:
new f866753 Read repair test with moving token should read at QUORUM
f866753 is described below
commit f866753b058fae2d73089710acd5628b7cff70c7
Author: Sam Tunnicliffe <[email protected]>
AuthorDate: Tue Sep 15 11:21:43 2020 +0100
Read repair test with moving token should read at QUORUM
Patch by Sam Tunnicliffe; reviewed by Ekaterina Dimitrova for
CASSANDRA-16049
---
.../org/apache/cassandra/distributed/test/ReadRepairTest.java | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git
a/test/distributed/org/apache/cassandra/distributed/test/ReadRepairTest.java
b/test/distributed/org/apache/cassandra/distributed/test/ReadRepairTest.java
index 6f91d9b..02310cb 100644
--- a/test/distributed/org/apache/cassandra/distributed/test/ReadRepairTest.java
+++ b/test/distributed/org/apache/cassandra/distributed/test/ReadRepairTest.java
@@ -124,10 +124,12 @@ public class ReadRepairTest extends TestBaseImpl
// prevent #4 from reading or writing to #3, so our QUORUM must
contain #2 and #4
// since #1 is taking over the range, this means any read-repair
must make it to #1 as well
- cluster.filters().verbs(READ_REQ.ordinal()).from(4).to(3).drop();
-
cluster.filters().verbs(READ_REPAIR_REQ.ordinal()).from(4).to(3).drop();
+ // (as a speculative repair in this case, as we prefer to send
repair mutations to the initial
+ // set of read replicas, which are 2 and 3 here).
+ cluster.filters().verbs(READ_REQ.id).from(4).to(3).drop();
+ cluster.filters().verbs(READ_REPAIR_REQ.id).from(4).to(3).drop();
assertRows(cluster.coordinator(4).execute("SELECT * FROM " +
KEYSPACE + ".tbl WHERE pk = ?",
- ConsistencyLevel.ALL, i),
+ ConsistencyLevel.QUORUM,
i),
row(i, 1, 1));
// verify that #1 receives the write
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
