You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (Issue Comment Edited) (JIRA)" <ji...@apache.org> on 2011/11/02 19:09:32 UTC
[jira] [Issue Comment Edited] (CASSANDRA-3430) Break Big Compaction
Lock apart
[ https://issues.apache.org/jira/browse/CASSANDRA-3430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142366#comment-13142366 ]
Jonathan Ellis edited comment on CASSANDRA-3430 at 11/2/11 6:08 PM:
--------------------------------------------------------------------
Hmm. That's true, but that also makes it more obvious that 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.
was (Author: jbellis):
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