Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1A7D4115DD for ; Wed, 10 Sep 2014 16:00:36 +0000 (UTC) Received: (qmail 12928 invoked by uid 500); 10 Sep 2014 16:00:35 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 12892 invoked by uid 500); 10 Sep 2014 16:00:35 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 12878 invoked by uid 99); 10 Sep 2014 16:00:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Sep 2014 16:00:35 +0000 Date: Wed, 10 Sep 2014 16:00:35 +0000 (UTC) From: "Marcus Eriksson (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-7810) tombstones gc'd before being locally applied MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-7810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14128639#comment-14128639 ] Marcus Eriksson commented on CASSANDRA-7810: -------------------------------------------- should be 2.0.11 in CHANGES - probably merge issue > tombstones gc'd before being locally applied > -------------------------------------------- > > Key: CASSANDRA-7810 > URL: https://issues.apache.org/jira/browse/CASSANDRA-7810 > Project: Cassandra > Issue Type: Bug > Environment: 2.1.0.rc6 > Reporter: Jonathan Halliday > Assignee: Marcus Eriksson > Fix For: 1.2.19, 2.0.11, 2.1.0 > > Attachments: 0001-7810-test-for-2.0.x.patch, 0001-track-gcable-tombstones-v2.patch, 0001-track-gcable-tombstones.patch, 0002-track-gcable-tombstones-for-2.0.patch, range_tombstone_test.py > > > # single node environment > CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy', 'replication_factor': 1 }; > use test; > create table foo (a int, b int, primary key(a,b)); > alter table foo with gc_grace_seconds = 0; > insert into foo (a,b) values (1,2); > select * from foo; > -- one row returned. so far, so good. > delete from foo where a=1 and b=2; > select * from foo; > -- 0 rows. still rainbows and kittens. > bin/nodetool flush; > bin/nodetool compact; > select * from foo; > a | b > ---+--- > 1 | 2 > (1 rows) > gahhh. > looks like the tombstones were considered obsolete and thrown away before being applied to the compaction? gc_grace just means the interval after which they won't be available to remote nodes repair - they should still apply locally regardless (and do correctly in 2.0.9) -- This message was sent by Atlassian JIRA (v6.3.4#6332)