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 0A432177E3 for ; Fri, 10 Oct 2014 00:22:11 +0000 (UTC) Received: (qmail 20882 invoked by uid 500); 10 Oct 2014 00:22:07 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 20843 invoked by uid 500); 10 Oct 2014 00:22:07 -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 20833 invoked by uid 99); 10 Oct 2014 00:22:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Oct 2014 00:22:07 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rcoli@eventbrite.com designates 209.85.215.51 as permitted sender) Received: from [209.85.215.51] (HELO mail-la0-f51.google.com) (209.85.215.51) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Oct 2014 00:22:03 +0000 Received: by mail-la0-f51.google.com with SMTP id ge10so2226767lab.38 for ; Thu, 09 Oct 2014 17:21:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=BPCsj2QAlo/d9HFSL5bDQPOjFHqcvYdpHSHG6YnGG80=; b=Do1T/zQ/gKX/UROnLlx8U6L3/JiZGGrGRYiPsihU+DF5V+xlnsc+PhgDKXL4+1bOYB H+KooNwWAHWKsQsOvoyFzAthOiPXroOL/cyNTGsTZpI2x8yB3Fy66Avv59t0Isw6HB+e MJ18rC66sDoDoGn/1f85391Khqn/ZvC2MAvIZL5ZAuxIVOvtdE87dMC1mtWPzDuumCox Vggl6mSGu/FPKfLH7ewmyq9LmBDpNpyruhNXdlbuKpiRTMJIODoWL4XunPxGzPpCWMX6 rNloO1u4adCorsUZo2REkUUEj0IwmUZbTOjZdhcoM2sMBg/GQf4ohA8eg6OlZUaZdCWL qYCQ== X-Gm-Message-State: ALoCoQl43HUir4ZfpyUPRq+lH+iwOpPD2fn4p6uDhWxvYWP1undOn5rMq/lXjamXeIXXo5f4l0Cq MIME-Version: 1.0 X-Received: by 10.112.65.5 with SMTP id t5mr773204lbs.82.1412900501995; Thu, 09 Oct 2014 17:21:41 -0700 (PDT) Received: by 10.114.187.168 with HTTP; Thu, 9 Oct 2014 17:21:41 -0700 (PDT) In-Reply-To: <71FD09CC-743B-4A2A-A9D0-3764C7617E04@fold3.com> References: <71FD09CC-743B-4A2A-A9D0-3764C7617E04@fold3.com> Date: Thu, 9 Oct 2014 17:21:41 -0700 Message-ID: Subject: Re: Deleting counters From: Robert Coli To: "user@cassandra.apache.org" Content-Type: multipart/alternative; boundary=001a11345628865c99050506883c X-Virus-Checked: Checked by ClamAV on apache.org --001a11345628865c99050506883c Content-Type: text/plain; charset=UTF-8 On Thu, Oct 9, 2014 at 3:29 PM, Robert Wille wrote: > What is the bad thing that happens (or can possibly happen) when a counter > is deleted? > You get totally wacky counter state if you, later, re-create and use it. https://issues.apache.org/jira/browse/CASSANDRA-6532 and https://issues.apache.org/jira/browse/CASSANDRA-7346 Have some good discussion. Is it safe to delete an entire row of counters? Not unless : a) you will never use that particular counter row again OR b) gc_grace_seconds has passed and you have repaired and run a major compaction on every node, such that 100% of such tombstones have been removed > Is there any 2.0.x version of Cassandra in which it is safe to delete > counters? See above, 2.0 is the same as any other version for this behavior. Is there an access pattern in which it is safe to delete counters in 2.0.x? > The summary of the above is that, in practice, it is only safe to delete counters if you plan to never use that particular counter row again. =Rob --001a11345628865c99050506883c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On T= hu, Oct 9, 2014 at 3:29 PM, Robert Wille <rwille@fold3.com> w= rote:
What is the bad thing that happens (or can possib= ly happen) when a counter is deleted?

<= div>You get totally wacky counter state if you, later, re-create and use it= .

https://issues.apache.org/jira/browse/CASSANDRA-6532
and
Have some good discussion.
Is it safe to delete an entire row of counters? <= /blockquote>
=C2=A0
Not unless :
a) you will never = use that particular counter row again
OR
b) gc_grac= e_seconds has passed and you have repaired and run a major compaction on ev= ery node, such that 100% of such tombstones have been removed
=C2= =A0
Is there any 2.0.x version of Cassandra = in which it is safe to delete counters?

See above, 2.0 is the same as any other version for this behavior.
=

Is there an access pattern in which it= is safe to delete counters in 2.0.x?

=
The summary of the above is that, in practice, it is only safe to dele= te counters if you plan to never use that particular counter row again.

=3DRob



--001a11345628865c99050506883c--