You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Michael Shuler (JIRA)" <ji...@apache.org> on 2014/07/29 21:08:39 UTC

[jira] [Resolved] (CASSANDRA-5469) Race condition between index building and scrubDirectories() at startup

     [ https://issues.apache.org/jira/browse/CASSANDRA-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Shuler resolved CASSANDRA-5469.
---------------------------------------

    Resolution: Duplicate

If CASSANDRA-5350 did not correct this behavior, please feel free to re-open.

> Race condition between index building and scrubDirectories() at startup
> -----------------------------------------------------------------------
>
>                 Key: CASSANDRA-5469
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5469
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.12, 1.1.10, 1.2.4
>            Reporter: amorton
>            Priority: Minor
>
> 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 ? 



--
This message was sent by Atlassian JIRA
(v6.2#6252)