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 8135149B1 for ; Tue, 21 Jun 2011 21:14:49 +0000 (UTC) Received: (qmail 91672 invoked by uid 500); 21 Jun 2011 21:14:47 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 91645 invoked by uid 500); 21 Jun 2011 21:14:47 -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 91637 invoked by uid 99); 21 Jun 2011 21:14:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Jun 2011 21:14:47 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of meatforums@gmail.com designates 209.85.216.179 as permitted sender) Received: from [209.85.216.179] (HELO mail-qy0-f179.google.com) (209.85.216.179) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Jun 2011 21:14:40 +0000 Received: by qyk29 with SMTP id 29so131319qyk.10 for ; Tue, 21 Jun 2011 14:14:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=dBKi3uo+6gKiVuPnvSZzbH7uRarwLDFNMUvWnmDxlNM=; b=W42DSNv896ghzyRVduxkZx0JsTbOP9E1q5TNCCDjViDy2YJbM9NAJuxuJN3Dkaxfon 7rqk9mfLK3P+Ib39f05StfhD423GSnJapt8WaoEP2XfLpe/XQsL8UvBWF2DGdw3/3BfK wytOFt9mfW1WA93uvogv+ckZ3Ct2MbnkgMW3o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=rU32fsva+IMDqj/Zrpit0UvO398YeQoB4QsiSCT/jcCN5khToaKc5SUXEsaUaK1Bnc Js6qiEiHy52lARzLDKUCVDIfdFWcQGOp2gHegixLVefClSyx3VxfqhW3K7VsQwxG3Xr5 fL99tHgRKy8uKkwgOe8fBAYLekWHsZ1AsJhPU= MIME-Version: 1.0 Received: by 10.229.136.1 with SMTP id p1mr5497934qct.218.1308690859628; Tue, 21 Jun 2011 14:14:19 -0700 (PDT) Received: by 10.229.217.81 with HTTP; Tue, 21 Jun 2011 14:14:19 -0700 (PDT) In-Reply-To: <4E01073B.6090200@dude.podzone.net> References: <4E00D52A.6040409@dude.podzone.net> <4E01073B.6090200@dude.podzone.net> Date: Tue, 21 Jun 2011 14:14:19 -0700 Message-ID: Subject: Re: Storing Accounting Data From: Anand Somani To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=00248c70feb5cf1b9004a63f55b6 X-Virus-Checked: Checked by ClamAV on apache.org --00248c70feb5cf1b9004a63f55b6 Content-Type: text/plain; charset=ISO-8859-1 Not sure if it is that simple, a quorum can fail with writes happening on some nodes (there is no rollback). Also there is no concept of atomic compare-and-swap. On Tue, Jun 21, 2011 at 2:03 PM, AJ wrote: > ** > On 6/21/2011 2:50 PM, Stephen Connolly wrote: > > how important are things like transactional consistency for you? > > would you have issues if only one side of a transfer was recorded? > > > Right. Both of those questions are about consistency. Isn't the simple > solution is to use QUORUM read/writes? > > cassandra, out of the box, on it's own, would not be ideal if the above > two things are important for you. > > you can add components to a system to help address these things, eg > zookeeper, etc. a reason why you moght do this is if you already use > cassandra in your app and are trying to limit the number of databases > > - Stephen > > --- > Sent from my Android phone, so random spelling mistakes, random nonsense > words and other nonsense are a direct result of using swype to type on the > screen > On 21 Jun 2011 18:30, "AJ" wrote: > > > --00248c70feb5cf1b9004a63f55b6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Not sure if it is that simple, a quorum can fail with writes happening on s= ome nodes (there is no rollback). Also there is no concept of atomic compar= e-and-swap.

On Tue, Jun 21, 2011 at 2:03 = PM, AJ <aj@dude= .podzone.net> wrote:
=20 =20 =20
On 6/21/2011 2:50 PM, Stephen Connolly wrote:

how important are things like transactional consistency for you?

would you have issues if only one side of a transfer was recorded?


Right.=A0 Both of those questions are about consistency.=A0 Isn't t= he simple solution is to use QUORUM read/writes?=A0

cassandra, out of the box, on it's own, would not be ideal if the above two things are important for you.

you can add components to a system to help address these things, eg zookeeper, etc. a reason why you moght do this is if you already use cassandra in your app and are trying to limit the number of databases

- Stephen

---
Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen

On 21 Jun 2011 18:30, "AJ" <<= a href=3D"mailto:aj@dude.podzone.net" target=3D"_blank">aj@dude.podzone.net= > wrote:


--00248c70feb5cf1b9004a63f55b6--