You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2011/02/17 21:28:26 UTC

[jira] Updated: (CASSANDRA-1585) Schema rename with compaction race

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

Brandon Williams updated CASSANDRA-1585:
----------------------------------------

    Fix Version/s:     (was: 0.7.2)
                   0.7.3

> Schema rename with compaction race
> ----------------------------------
>
>                 Key: CASSANDRA-1585
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1585
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Stu Hood
>            Assignee: Gary Dusbabek
>            Priority: Critical
>             Fix For: 0.7.3
>
>
> We observed what appeared to be a race between an ongoing compaction and a system_drop_cf call. The destination SSTable of the compaction was not removed by the drop, so it remained in the data directory. Recreating a CF of the same name caused the SSTable to become active again (or to at least show in the gossiped load).

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira