[CASSANDRA-13069] Local batchlog for MV may not be correctly written on node movements

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.15, 3.11.1, 4.0-alpha1, 4.0
• Component/s: Feature/Materialized Views
• Bug Category: Correctness - Unrecoverable Corruption / Loss
• Severity: Normal
• Assignee: Paulo Motta
• Reporter: Sylvain Lebresne

Authors

Paulo Motta

Reviewers

Sylvain Lebresne

• Created: 21/Dec/16 16:02
• Updated: 15/May/20 08:03
• Resolved: 12/Sep/17 13:40

Description

Unless I'm really reading this wrong, I think the code here, which comes from CASSANDRA-10674, isn't working properly.

More precisely, I believe we can have both paired and unpaired mutations, so that both if can be taken, but if that's the case, the 2nd write to the batchlog will basically overwrite (remove) the batchlog write of the 1st if and I don't think that's the intention. In practice, this means "paired" mutation won't be in the batchlog, which mean they won't be replayed at all if they fail.

Issue Links

• causes: CASSANDRA-14251 View replica is not written to pending endpoint when base replica is also view replica
• is depended upon by: CASSANDRA-13162 Batchlog replay is throttled during bootstrap, creating conditions for incorrect query results on materialized views