Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 698D2E499 for ; Mon, 28 Jan 2013 02:03:17 +0000 (UTC) Received: (qmail 88801 invoked by uid 500); 28 Jan 2013 02:03:14 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 88774 invoked by uid 500); 28 Jan 2013 02:03:14 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 88765 invoked by uid 99); 28 Jan 2013 02:03:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Jan 2013 02:03:14 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [208.113.200.5] (HELO homiemail-a52.g.dreamhost.com) (208.113.200.5) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Jan 2013 02:03:09 +0000 Received: from homiemail-a52.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a52.g.dreamhost.com (Postfix) with ESMTP id EBF7D6B82F3 for ; Sun, 27 Jan 2013 18:02:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thelastpickle.com; h=from :content-type:message-id:mime-version:subject:date:references:to :in-reply-to; s=thelastpickle.com; bh=DUrg+XPujbhdlx2J620L8pT5Z5 k=; b=seFALJg31rl2a+cP/SLTqJVs42Gq07VgXYDxDW+3jI3S/1Qif+RRgK9Db7 Ta34N3C+GyUCIwLp+jluf6ameQeOsXkX7Ds1Z1fXvbQEQJsLL2SSV9Z1/QzV3fPa uXy5GxiRYCuuXScH59iRUs6he+3tarkZvWFrguPwRVmvzlSEo= Received: from [172.16.1.8] (unknown [203.86.207.101]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: aaron@thelastpickle.com) by homiemail-a52.g.dreamhost.com (Postfix) with ESMTPSA id 27B5E6B8269 for ; Sun, 27 Jan 2013 18:02:48 -0800 (PST) From: aaron morton Content-Type: multipart/alternative; boundary="Apple-Mail=_2D36396F-8CD1-47D8-88C5-C3F879C2F7EC" Message-Id: <3B09CFC2-0559-4AED-AE5A-AA2682720C0F@thelastpickle.com> Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: Issue when deleting Cassandra rowKeys. Date: Mon, 28 Jan 2013 15:02:43 +1300 References: To: user@cassandra.apache.org In-Reply-To: X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_2D36396F-8CD1-47D8-88C5-C3F879C2F7EC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Deletes must be written to disk otherwise they are lost.=20 Cheers ----------------- Aaron Morton Freelance Cassandra Developer New Zealand @aaronmorton http://www.thelastpickle.com On 28/01/2013, at 3:29 AM, Kasun Weranga wrote: > Hi, >=20 > After running compaction tombstones get removed. So It seems like only = setting GC grace seconds to lower value is not enough. Am I correct ? >=20 > Thanks, > Kasun >=20 > On Sun, Jan 27, 2013 at 1:31 PM, Kasun Weranga = wrote: > Hi, >=20 > On Sun, Jan 27, 2013 at 12:05 AM, Michael Kjellman = wrote: > What is your gc_grace set to? >=20 > Thanks for the info.=20 >=20 > I tried setting GcGraceSeconds for the column family to 0 since I have = only one Cassandra node. still I can see the same behavior.=20 >=20 > ColumnFamily: bam_phone_retail_store_kpi > Key Validation Class: org.apache.cassandra.db.marshal.BytesType > Default column value validator: = org.apache.cassandra.db.marshal.BytesType > Columns sorted by: org.apache.cassandra.db.marshal.BytesType > GC grace seconds: 0 > Compaction min/max thresholds: 4/32 > Read repair chance: 0.0 > DC Local Read repair chance: 0.0 > Replicate on write: false > Caching: KEYS_ONLY > Bloom Filter FP chance: default > Compaction Strategy: = org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy > Compression Options: > chunk_length_kb: 128 > sstable_compression: = org.apache.cassandra.io.compress.SnappyCompressor >=20 >=20 > I am using Cassandra 1.1.3. Appreciate your help on solving this. >=20 > Thanks, > Kasun.=20 >=20 > =20 >=20 > Are your findings before or after this time after the deletion? >=20 > From: Kasun Weranga > Reply-To: "user@cassandra.apache.org" > Date: Saturday, January 26, 2013 10:33 AM > To: "user@cassandra.apache.org" , = "dev@cassandra.apache.org" > Subject: Issue when deleting Cassandra rowKeys. >=20 > Hi all, >=20 > When I delete some rowkeys programmatically I can see two rowkeys = remains in the column family. I think it is due to tombstones. Is there = a way to remove it when deleting rowkeys. Can I run compaction = programmatically after deletion? will it remove all these remaining = rowkeys.=20 >=20 > Thanks, > Kasun.=20 >=20 >=20 --Apple-Mail=_2D36396F-8CD1-47D8-88C5-C3F879C2F7EC Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1
http://www.thelastpickle.com

On 28/01/2013, at 3:29 AM, Kasun Weranga <kasunw@wso2.com> wrote:

Hi,

After running compaction = tombstones get removed. So It seems like only setting GC grace seconds = to lower value is not enough. Am I correct = ?

Thanks,
Kasun

On Sun, Jan 27, 2013 at 1:31 PM, Kasun Weranga <kasunw@wso2.com> wrote:
Hi,

On = Sun, Jan 27, 2013 at 12:05 AM, Michael Kjellman <mkjellman@barracuda.com> wrote:
What is your gc_grace set to?

Thanks for the = info. 

I tried setting GcGraceSeconds for = the column family to 0 since I have only one Cassandra node. still I can = see the same behavior. 

    ColumnFamily: = bam_phone_retail_store_kpi
      Key Validation = Class: org.apache.cassandra.db.marshal.BytesType
    =   Default column value validator: = org.apache.cassandra.db.marshal.BytesType
      Columns sorted by: = org.apache.cassandra.db.marshal.BytesType
      = GC grace seconds: 0
      Compaction min/max = thresholds: 4/32
      Read repair chance: = 0.0
      DC Local Read repair chance: = 0.0
      Replicate on write: false
  =     Caching: KEYS_ONLY
      Bloom = Filter FP chance: default
      Compaction = Strategy: = org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy
      Compression Options:
    =     chunk_length_kb: 128
        = sstable_compression: = org.apache.cassandra.io.compress.SnappyCompressor


I am using Cassandra 1.1.3. Appreciate your help = on solving this.

Thanks,
Kasun. 

 

Are your findings before or after this time after = the deletion?

From: Kasun Weranga <kasunw@wso2.com>
Reply-To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Date: Saturday, January 26, = 2013 10:33 AM
To: "user@cassandra.apache.org" <user@cassandra.apache.org>, "dev@cassandra.apache.org" <dev@cassandra.apache.org>
Subject: Issue when deleting = Cassandra rowKeys.

Hi all,

When I delete some rowkeys programmatically I can = see two rowkeys remains in the column family. I think it is due to = tombstones. Is there a way to remove it when deleting rowkeys. Can I run = compaction programmatically after deletion? will it remove all these remaining = rowkeys. 

Thanks,
Kasun. 

<= /div>


= --Apple-Mail=_2D36396F-8CD1-47D8-88C5-C3F879C2F7EC--