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] [Commented] (CASSANDRA-2786) After a minor compaction, deleted key-slices are visible again
Date Tue, 21 Jun 2011 12:27:47 GMT

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

Jonathan Ellis commented on CASSANDRA-2786:
-------------------------------------------

+1

(can we make the "testing" constructor package-local?)

> After a minor compaction, deleted key-slices are visible again
> --------------------------------------------------------------
>
>                 Key: CASSANDRA-2786
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2786
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8.0
>         Environment: Reproduced on single Cassandra node (CentOS 5.5)
> Reproduced on single Cassandra node (Windows Server 2008)
>            Reporter: rene kochen
>         Attachments: 0001-Fix-wrong-purge-of-deleted-cf.patch, CassandraIssue.zip, CassandraIssueJava.zip
>
>
> After a minor compaction, deleted key-slices are visible again.
> Steps to reproduce:
> 1) Insert a row named "test".
> 2) Insert 500000 rows. During this step, row "test" is included in a major compaction:
>    file-1, file-2, file-3 and file-4 compacted to file-5 (includes "test").
> 3) Delete row named "test".
> 4) Insert 500000 rows. During this step, row "test" is included in a minor compaction:
>    file-6, file-7, file-8 and file-9 compacted to file-10 (should include tombstoned
"test").
> After step 4, row "test" is live again.
> Test environment:
> Single node with empty database.
> Standard configured super-column-family (I see this behavior with several gc_grace settings
(big and small values):
> create column family Customers with column_type = 'Super' and comparator = 'BytesType;
> In Cassandra 0.7.6 I observe the expected behavior, i.e. after step 4, the row is still
deleted.
> I've included a .NET program to reproduce the problem. I will add a Java version later
on.

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

        

Mime
View raw message