cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3430) Break Big Compaction Lock apart
Date Wed, 02 Nov 2011 18:09:32 GMT

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

Jonathan Ellis commented on CASSANDRA-3430:
-------------------------------------------

Hmm.  If we do that then we could potentially have data flushed post-"main" truncate, whose
indexes get truncated, so the index won't actually match the data file.  Right?

I think that either we need to make index compaction lock both the base CF as well as itself,
or just bag this for 1.0 and only do it in 1.1.  Kind of inclined towards the latter.
                
> Break Big Compaction Lock apart
> -------------------------------
>
>                 Key: CASSANDRA-3430
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3430
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>              Labels: compaction
>             Fix For: 1.0.2
>
>         Attachments: 3430-1.0.txt, 3430-1.1.txt
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message