[CASSANDRA-18653] Avoid unnecessary index builds and validations - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Resolved
Priority: Normal
Resolution: Duplicate
Fix Version/s: None
Component/s: Feature/SAI
Labels:
None

Epic Link:
Storage Attached Indexes (Phase 2)
Change Category:
Performance
Complexity:
Normal
Platform:

All
Impacts:

None

Description

In the testing of ~~CASSANDRA-18490~~ it was noted that the SSTableAddedNotification will trigger an index build that will always build the column index components even if they already exist and are valid.

The same notification is also handled by the StorageAttachedIndexGroup that can validate the components. This can lead to the components being validated more than is necessary.

We should coordinate these notification handlers so there is no overlap of responsibility.

Attachments

Issue Links

duplicates

CASSANDRA-18670 Importer should build SSTable indexes successfully before making new SSTables readable

Resolved

is related to

CASSANDRA-18490 Checksum per-SSTable and per-column SAI components after streaming

Resolved

relates to

CASSANDRA-18656 Secondary indexes either violate consistency or become unavailable when post-streaming index builds fail

Open

CASSANDRA-18670 Importer should build SSTable indexes successfully before making new SSTables readable

Resolved

Activity

People

Assignee:: Mike Adamson

Reporter:: Mike Adamson

Authors:: Mike Adamson

Reviewers:: Caleb Rackliffe

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 06/Jul/23 15:27

Updated:: 24/Jul/23 22:39

Resolved:: 24/Jul/23 22:39