[CASSANDRA-19400] IndexStatusManager needs to prioritize SUCCESS over UNKNOWN states to maximize availability

• Type: Bug
• Status: Patch Available
• Priority: Low
• Resolution: Unresolved
• Fix Version/s: 5.0.x, 5.x
• Component/s: Feature/SAI
• Epic Link: Storage Attached Indexes (Phase 3)
• Bug Category: Availability - Unavailable
• Severity: Low
• Complexity: Normal
• Discovered By: Fuzz Test
• Platform: All

Test and Documentation Plan

additions to IndexAvailabilityTest?

• Assignee: Arun Ganesh
• Reporter: Caleb Rackliffe

Authors

Arun Ganesh

Reviewers

Caleb Rackliffe

• Created: 15/Feb/24 02:55
• Updated: 5 days ago 17:07

Description

IndexStatusManager is responsible for knowing what SAI indexes are queryable across the ring, endpoint by endpoint. There are two statuses that SAI treats as queryable, but it should not treat them equally. BUILD_SUCCEEDED means the index is definitely available and should be able to serve queries without issue. UNKNOWN indicates that the status of the index hasn’t propagated yet to this coordinator. It may be just fine, or it may not be. If it isn’t a query will not return incorrect results, but it will fail. If there are enough BUILD_SUCCEEDED replicas, we should ignore UNKNOWN replicas and maximize availability. If the UNKNOWN replica is going to become BUILD_SUCCEEDED shortly, it will happily start taking requests at that point and spread the load. If not, we’ll avoid futile attempts to query it too early.

Issue Links

• links to: GitHub Pull Request #3350