Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 66961 invoked from network); 29 Mar 2010 17:56:19 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 29 Mar 2010 17:56:19 -0000 Received: (qmail 29229 invoked by uid 500); 29 Mar 2010 17:56:18 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 29204 invoked by uid 500); 29 Mar 2010 17:56:18 -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 29196 invoked by uid 99); 29 Mar 2010 17:56:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Mar 2010 17:56:18 +0000 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=AWL,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ewhauser@gmail.com designates 209.85.212.44 as permitted sender) Received: from [209.85.212.44] (HELO mail-vw0-f44.google.com) (209.85.212.44) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Mar 2010 17:56:13 +0000 Received: by vws9 with SMTP id 9so112270vws.31 for ; Mon, 29 Mar 2010 10:55:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:received:message-id:subject:to:content-type; bh=gaOZEs3BTC1T7KzW4giKhdoYcHHgnl9GKRA7T5k+vik=; b=XSoU08yy7MuWCslG2HEahgvCv5KHtHPOmKaTBPNIQpdcjVdiw/Kxn7VQ7d2Z0t9rI8 //C0zVMtwxXnsZwUBOZT42faRUebQRVu9jXXrcTRm9A2XUA02vprFf/cUgMpTtec5JGM euRXp7f7H+rn/frTfWIxCk2bgd7Vz096PeKYg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=Ro+vtIHOtUATSVX47Qv5n54KgOSbJ3hwmpoQK+JGTcthRMEpPUUilc5mVM4GjfGQSC jEePvNMjQrgeyf3qrDL5lXKhumoyzraffdzd9/lPiIGCLb5+5O5ZB7p+f3jcsl7PcuAq RE0SVJiHFphIns4hzt3qWA3NnncJ5f4lgrhYg= MIME-Version: 1.0 Received: by 10.220.166.70 with HTTP; Mon, 29 Mar 2010 10:55:32 -0700 (PDT) In-Reply-To: References: From: Eric Hauser Date: Mon, 29 Mar 2010 13:55:32 -0400 Received: by 10.220.127.96 with SMTP id f32mr3299606vcs.32.1269885352218; Mon, 29 Mar 2010 10:55:52 -0700 (PDT) Message-ID: <2b4765e71003291055g2aceb04fn72f75e9da08f9902@mail.gmail.com> Subject: Re: How reliable is cassandra? To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=0016e68ee02e5322880482f439a9 --0016e68ee02e5322880482f439a9 Content-Type: text/plain; charset=ISO-8859-1 Does the information is the below link about Cassandra and replication over WAN have any merit or is it just FUD? http://www.roadtofailure.com/2009/10/29/hbase-vs-cassandra-nosql-battle/ On Mon, Mar 29, 2010 at 1:51 PM, Jonathan Ellis wrote: > Cassandra is an excellent choice for systems that Can't Lose Data. > > - real single-server durability (set CommitLogSync to "batch"), not > just "hope it replicates somewhere before you lose power" > - best multi-DC replication anywhere > - immutable data files mean it's very difficult to introduce corruption > bugs > - SnapshotBeforeCompaction option allows taking a snapshot of all > your data files before replacing them with newer ones, so you can roll > back to just before any compaction (as long as you have enough disk > space to hold the snapshots of course) > > -Jonathan > > On Mon, Mar 29, 2010 at 12:31 PM, Matthew Stump > wrote: > > Am I crazy to want to switch our server's primary data store from > postgres to cassandra? This is a system used by banks and governments to > store crypto keys which absolutely can not be lost. > --0016e68ee02e5322880482f439a9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Does the information is the below link about Cassandra and replication over= WAN have any merit or is it just FUD?

http://= www.roadtofailure.com/2009/10/29/hbase-vs-cassandra-nosql-battle/


On Mon, Mar 29, 2010 at 1:51 PM, Jonatha= n Ellis <jbellis@= gmail.com> wrote:
Cassandra is an excellent choice for systems that Can't Lose Data.

=A0- real single-server durability (set CommitLogSync to "batch")= , not
just "hope it replicates somewhere before you lose power"
=A0- best multi-DC replication anywhere
=A0- immutable data files mean it's very difficult to introduce corrupt= ion bugs
=A0- SnapshotBeforeCompaction option allows taking a snapshot of all
your data files before replacing them with newer ones, so you can roll
back to just before any compaction (as long as you have enough disk
space to hold the snapshots of course)

-Jonathan

On Mon, Mar 29, 2010 at 12:31 PM, Matthew Stump <mrevilgnome@gmail.com> wrote:
> Am I crazy to want to switch our server's primary data store from = postgres to cassandra? =A0This is a system used by banks and governments to= store crypto keys which absolutely can not be lost.

--0016e68ee02e5322880482f439a9--