[CASSANDRA-10130] Node failure during 2i update after streaming can have incomplete 2i when restarted

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 4.0-alpha1, 4.0
• Component/s: Legacy/Coordination
• Severity: Low
• Assignee: Andres de la Peña
• Reporter: Yuki Morishita

Authors

Andres de la Peña

Reviewers

Paulo Motta, Sergio Bossa

• Created: 19/Aug/15 17:40
• Updated: 07/Jul/23 22:58
• Resolved: 23/Jun/17 10:06

Description

Since MV/2i update happens after SSTables are received, node failure during MV/2i update can leave received SSTables live when restarted while MV/2i are partially up to date.

We can add some kind of tracking mechanism to automatically rebuild at the startup, or at least warn user when the node restarts.

Issue Links

• is depended upon by: CASSANDRA-13606 Improve handling of 2i initialization failures
• is related to: CASSANDRA-18656 Secondary indexes either violate consistency or become unavailable when post-streaming index builds fail
• relates to: CASSANDRA-9308 Decouple streaming from secondary index rebuild