Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 23568 invoked from network); 24 May 2010 15:48:18 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 24 May 2010 15:48:18 -0000 Received: (qmail 64438 invoked by uid 500); 24 May 2010 15:48:17 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 64421 invoked by uid 500); 24 May 2010 15:48:17 -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 64413 invoked by uid 99); 24 May 2010 15:48:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 May 2010 15:48:17 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of stevelihn@gmail.com designates 72.14.220.156 as permitted sender) Received: from [72.14.220.156] (HELO fg-out-1718.google.com) (72.14.220.156) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 May 2010 15:48:09 +0000 Received: by fg-out-1718.google.com with SMTP id 16so339222fgg.7 for ; Mon, 24 May 2010 08:47:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=tTOKPrTJPGTQ696l7pe632Mgv4/Mn1PsPz0uKaVFr30=; b=kUakzELC3xi2DBuBwjKAnz0UaziTaplqQtajwWl3yQPj4UfodOcgwh9DvFRHu9tRdW HsBvEcqYzWqc+WGzyIQvEUXX1Ty/ixzRNP41FvgowkJj8ga2cThECqjciCIP2irhjFKT t6rbTuAcpTAAzlgdskOUtcCT9lMWTx++EI/Zg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=F4kcz1XD37QhxGCqxaKnUtCdXgzYyVxMBGQFtOSXpGACtCzNtD8zdYggEO7jBEzS36 RigqHYX6pHiIwlmS31y9H/wweaMLpdjZXckV4xm5TkkLxTUthjC9EoVSrwW9ifOsOrwC C7d8dyeux/R7xCTxiUL5G5CuLh9anLBbuCXs8= MIME-Version: 1.0 Received: by 10.102.214.32 with SMTP id m32mr3984076mug.42.1274716068835; Mon, 24 May 2010 08:47:48 -0700 (PDT) Received: by 10.103.233.6 with HTTP; Mon, 24 May 2010 08:47:48 -0700 (PDT) Date: Mon, 24 May 2010 11:47:48 -0400 Message-ID: Subject: Cassandra data loss From: Steve Lihn To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=00163642697578f076048758f6e7 X-Virus-Checked: Checked by ClamAV on apache.org --00163642697578f076048758f6e7 Content-Type: text/plain; charset=UTF-8 I am evaluating Cassandra as a candidate for our next-gen database. One of my colleagues told me that "it's not recommended to use it as your system of Record because it CAN lose data". Can someone with architecture understanding shed some light on under what circumstance Cassandra cluster can either lose data or become inconsistent ? (a node in a cluster crashes, network partitions, I/O glitches, etc.) Thanks, Steve --00163642697578f076048758f6e7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I am evaluating Cassandra as a candidate for our next-gen database. One of = my colleagues told me that " it's not recommended to use it as your system of Record because it CAN lose data". Can someone with architecture unders= tanding shed some light on under what circumstance Cassandra cluster can ei= ther lose data or become inconsistent ? (a node in a cluster crashes, netwo= rk partitions, I/O glitches, etc.)

Thanks,
Steve
--00163642697578f076048758f6e7--