cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Dusbabek (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1585) Schema change with compaction race
Date Mon, 27 Dec 2010 14:48:06 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975264#action_12975264
] 

Gary Dusbabek commented on CASSANDRA-1585:
------------------------------------------

bq. what if we named the files by cfid instead of cfname, to handle rename?
The last time I looked, there was one part of code that still sent the CF name as part of
its serialized form.  I thought it was CFSerializer, but it appears to be using ids.  

I'll take a closer look to see if this is possible.  If we're not playing fast and loose with
CFnames in messages, I think it will work.

> Schema change 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.1
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message