Details
-
Bug
-
Status: Resolved
-
Low
-
Resolution: Duplicate
-
None
-
None
-
None
-
Low
Description
From user group http://www.mail-archive.com/user@cassandra.apache.org/msg29207.html
In CassandraDaemon.setup() the call to SystemTable.checkHealth() results in the CFS's being created. As part of their creation they kick of async secondary index build if the index is not marked as built (SecondaryIndexManager.addIndexedColumn()). Later in CD.setup() the call is made to scrub the data dirs and this can race with the tmp files created by the index rebuild. The result is an error that prevents the node starting.
Should we delay rebuilding secondary indexes until after startup has completed or rebuild them synchronously ?
Attachments
Issue Links
- is related to
-
CASSANDRA-5350 Fix ColumnFamily opening race
- Resolved