From user-return-31930-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Fri Feb 15 18:14:10 2013 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 3DFC2E9EA for ; Fri, 15 Feb 2013 18:14:10 +0000 (UTC) Received: (qmail 23563 invoked by uid 500); 15 Feb 2013 18:14:07 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 23538 invoked by uid 500); 15 Feb 2013 18:14: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 23530 invoked by uid 99); 15 Feb 2013 18:14:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Feb 2013 18:14:07 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_FRT_BELOW2 X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of vhmolinar@gmail.com designates 209.85.217.181 as permitted sender) Received: from [209.85.217.181] (HELO mail-lb0-f181.google.com) (209.85.217.181) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Feb 2013 18:13:59 +0000 Received: by mail-lb0-f181.google.com with SMTP id gm6so2806958lbb.40 for ; Fri, 15 Feb 2013 10:13:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=9cTC13uTO1UueLe/gipw4r0aUC4+IymRzJpfKaBU1RA=; b=gC7Oma3R7YDtB1uZhYf3CZgrXaYvDRKkUuB+CxYyk5pqybxJ8JE9fM/87Z31jJoNk1 v+E3L/cWv+3FoKAx3Fu/8xOe0fgFpdbpLYOQVXS0EDdbUWkVrdvtaZ8ES6S2if6YNe+w 3J7zW4AJsO3NgxKuX9DC29ADM+YLo0NuyGN0brBG+Wp8TOjueYVDoeS2HUppWdC/ZeaZ xFgBrSiiWm6YCB5EKEzuUDRffmPqPIv1Tt3x5AZfleGhQU+iNYdNFqkquHZztB4kcTIi sKgFS7cJkC8zkGyiRL4szEcXHY7VdzmMuBDSaJYaaxiQ/YFZsMUX3SHHGmV96oTF52Ih WltQ== X-Received: by 10.152.105.244 with SMTP id gp20mr2354617lab.34.1360952019085; Fri, 15 Feb 2013 10:13:39 -0800 (PST) MIME-Version: 1.0 Received: by 10.114.48.9 with HTTP; Fri, 15 Feb 2013 10:13:19 -0800 (PST) From: =?ISO-8859-1?Q?V=EDctor_Hugo_Oliveira_Molinar?= Date: Fri, 15 Feb 2013 16:13:19 -0200 Message-ID: Subject: Deletion consistency To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=f46d04083877a76a2a04d5c75516 X-Virus-Checked: Checked by ClamAV on apache.org --f46d04083877a76a2a04d5c75516 Content-Type: text/plain; charset=ISO-8859-1 hello everyone! I have a column family filled with event objects which need to be processed by query threads. Once each thread query for those objects(spread among columns bellow a row), it performs a delete operation for each object in cassandra. It's done in order to ensure that these events wont be processed again. Some tests has showed me that it works, but sometimes i'm not getting those events deleted. I checked it through cassandra-cli,etc. So, reading it (http://wiki.apache.org/cassandra/DistributedDeletes) I came to a conclusion that I may be reading old data. My cluster is currently configured as: 2 nodes, RF1, CL 1. In that case, what should I do? - Increase the consistency level for the write operations( in that case, the deletions ). In order to ensure that those deletions are stored in all nodes. or - Increase the consistency level for the read operations. In order to ensure that I'm reading only those yet processed events(deleted). ? - Thanks in advance --f46d04083877a76a2a04d5c75516 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable hello everyone!

I have a column family filled with event objects which = need to be processed by query threads.
Once each thread query for= those objects(spread among columns bellow a row), it performs a delete ope= ration for each object in cassandra.
It's done in order to ensure that these events wont be processed a= gain.
Some tests has showed me that it works, but sometimes i'= ;m not getting those events deleted. I checked it through cassandra-cli,etc= .

So, reading it (http://wiki.apache.org/cassandra/DistributedDelete= s) I came to a conclusion that I may be reading old data.
My cluster is currently configured as: 2 nodes, RF1, CL 1.
In that case, what should I do?

- Increase the consisten= cy level for the write operations( in that case, the deletions ). In order = to ensure that those deletions are stored in all nodes.
or
- Increase the consistency level for the read operations. In order to = ensure that I'm reading only those yet processed events(deleted).
=

?

-
Thanks in advanc= e


--f46d04083877a76a2a04d5c75516--