cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergio Bossa (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-13725) Secondary indexes are always rebuilt at startup
Date Mon, 24 Jul 2017 13:50:02 GMT


Sergio Bossa updated CASSANDRA-13725:

This is caused by calling {{SIM#markIndexesBuilding}} when creating the index during column
family initialization, which marks the index as "not built" and causes the index initialization
task to rebuild it.

Given there's no need to mark the index when a new column family is created (as the index
will be "not built" by definition and there can't be any concurrent indexing), we can just
pass a boolean up to {{createIndex()}} to distinguish between index creation at different
times, i.e. when a column family is [created|]
or [reloaded|].

Such solution is implemented in the following patch, with a new dtest verifying it:

Test runs are in progress on our internal CI and I will report results as soon as they're

> Secondary indexes are always rebuilt at startup
> -----------------------------------------------
>                 Key: CASSANDRA-13725
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Secondary Indexes
>            Reporter: Sergio Bossa
>            Assignee: Sergio Bossa
>            Priority: Critical
>             Fix For: 4.0
> Following CASSANDRA-10130, a bug has been introduced that causes a 2i to be rebuilt at
startup, even if such index is already built.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message