cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-5469) Race condition between index building and scrubDirectories() at startup
Date Tue, 19 Nov 2013 23:55:22 GMT

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

Jonathan Ellis updated CASSANDRA-5469:
--------------------------------------

    Priority: Minor  (was: Major)

> 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.1#6144)

Mime
View raw message