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

Agile Board

Attach files

Attach Screenshot

Bulk Copy Attachments

Bulk Move Attachments

Voters

Watch issue

Watchers

Create sub-task

Convert to sub-task

Move

Link

Clone

Labels

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Bug
Status: Resolved
Priority: Low
Resolution: Fixed
Fix Version/s: 5.0.1, 5.1
Component/s: Feature/SAI
Labels:
None

Epic Link:
Storage Attached Indexes (Phase 3)
Bug Category:
Availability - Unavailable
Severity:
Low
Complexity:
Normal
Discovered By:
Fuzz Test
Platform:

All
Impacts:

None
Since Version:

5.0-alpha1
Source Control Link:

https://github.com/apache/cassandra/commit/273975ef26e5de1a10a98c0df364cb67fa7830e3
Test and Documentation Plan:

Hide

new unit tests in IndexStatusManagerTest

Show
new unit tests in IndexStatusManagerTest

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.