cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-2279) Tombstones not collected post-repair
Date Wed, 09 Mar 2011 15:36:59 GMT

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

Sylvain Lebresne commented on CASSANDRA-2279:
---------------------------------------------

I'm not able to reproduce. And I don't see why repair would screw up with tombstones collection.
Only compaction should remove them and repair shouldn't have anything to do with this. If
sstable2json is the only one to show it, it's even weirder (that is, listing with the cli
should also show an empty row if there was problem with tombstone collection).

Are you sure you compacted node 2 (on which the empty row showed up) ? Are you sure there
wasn't a Queue-2527-Compacted file alongside Queue-2527-Data.db ? Are you sure node 2 local
time wasn't highly out of sync with node 1 ?

> Tombstones not collected post-repair
> ------------------------------------
>
>                 Key: CASSANDRA-2279
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2279
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 0.6
>            Reporter: Joaquin Casares
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 0.6.13, 0.7.4
>
>
> The keys would only show up in sstables2json and look like this:
> (root@aps4):/opt/cassandra/storage/queue/data/Panama Wed Feb 23 07:24:34am 
> ===> /opt/cassandra/bin/sstable2json Queue-2527-Data.db -k waq:publicMessageIndexingWorkArea:PUM8a65ce95-9d35-4941-928c-dd5965e8b29b

> 2011-02-23 07:24:43,710 INFO [org.apache.cassandra.config.DatabaseDescriptor] - DiskAccessMode
'auto' determined to be mmap, indexAccessMode is mmap 
> 2011-02-23 07:24:43,972 INFO [org.apache.cassandra.io.SSTableReader] - Opening /opt/cassandra/storage/queue/data/Panama/Queue-2527-Data.db

> { 
> "waq:publicMessageIndexingWorkArea:PUM8a65ce95-9d35-4941-928c-dd5965e8b29b": [] 
> } 
> (root@aps4):/opt/cassandra/storage/queue/data/Panama Wed Feb 23 07:24:44am 
> ===>
> The steps that I took to reproduce it were:
> Create a keyspace, column family, and a key
> Delete the key on Node 1 using the cli (del cf['key'];)
> Flush 
> Repair on a cluster with more than 1 node
> Wait GCSeconds 
> Compact
> And the empty row would appear on Node 2
> However, when I was able to get rid of the empty rows, I was following these steps on
a single machine: 
> Create a keyspace, column family, and a key
> Delete the key
> Flush
> Sample write (writing to some temporary key)
> Deleting the attribute to that temporary key (not the entire key)
> Flush
> Compact
> or these steps:
> Create a keyspace, column family, and a key
> Delete the key
> Flush 
> Wait GCseconds
> Compact

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

Mime
View raw message