[CASSANDRA-11477] MerkleTree mismatch when a cell is shadowed by a range tombstone in different SSTables

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Duplicate
• Labels: repair
• Severity: Normal
• Assignee: Fabien Rousseau
• Reporter: Fabien Rousseau

Authors

Fabien Rousseau

Reviewers

Branimir Lambov

• Created: 01/Apr/16 15:44
• Updated: 16/Apr/19 09:30
• Resolved: 04/Jul/16 11:10

Description

Below is a script which allows to reproduce the problem:

ccm create test -v 2.1.13 -n 2 -s
ccm node1 cqlsh
CREATE KEYSPACE test_rt WITH replication = {'class': 'SimpleStrategy', 'replication_factor': 2};
USE test_rt;
CREATE TABLE IF NOT EXISTS table1 (
    c1 text,
    c2 text,
    c3 text,
    PRIMARY KEY ((c1), c2)
);
INSERT INTO table1 (c1, c2, c3) VALUES ( 'a', 'b', 'c');
ctrl ^d
# now flush only one of the two nodes
ccm node1 flush 
ccm node1 cqlsh
USE test_rt;
DELETE FROM table1 WHERE c1 = 'a' AND c2 = 'b';
ctrl ^d
ccm node1 repair test_rt table1
# now grep the log and observe that there was some inconstencies detected between nodes (while it shouldn't have detected any)
ccm node1 showlog | grep "out of sync"

The wrong hash will be computed on node1, which will include the previously deleted cell, thus resulting in a MT mismatch.

This is due to the fact that, in LazilyCompactedRow, the RT is not added into the RT tracker (in fact, it's added only if it is GCable, but should always be added).

Issue Links

• Is contained by: CASSANDRA-11349 MerkleTree mismatch when multiple range tombstones exists for the same partition and interval
• is related to: CASSANDRA-11349 MerkleTree mismatch when multiple range tombstones exists for the same partition and interval