Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 39461 invoked from network); 9 Jun 2010 05:46:26 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 9 Jun 2010 05:46:26 -0000 Received: (qmail 16081 invoked by uid 500); 9 Jun 2010 05:46:25 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 16035 invoked by uid 500); 9 Jun 2010 05:46:25 -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 16027 invoked by uid 99); 9 Jun 2010 05:46:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Jun 2010 05:46:25 +0000 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=AWL,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.212.44] (HELO mail-vw0-f44.google.com) (209.85.212.44) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Jun 2010 05:46:18 +0000 Received: by vws9 with SMTP id 9so1074284vws.31 for ; Tue, 08 Jun 2010 22:45:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.59.30 with SMTP id j30mr1598315qah.143.1276062356874; Tue, 08 Jun 2010 22:45:56 -0700 (PDT) Received: by 10.229.236.71 with HTTP; Tue, 8 Jun 2010 22:45:56 -0700 (PDT) Date: Tue, 8 Jun 2010 23:45:56 -0600 Message-ID: Subject: Data loss and corruption From: Hector Urroz To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=00c09f9235fe7e28bb0488926bc5 --00c09f9235fe7e28bb0488926bc5 Content-Type: text/plain; charset=ISO-8859-1 Hi all, We're starting to prototype Cassandra for use in a production system and became concerned about data corruption after reading the excellent article: http://blog.evanweaver.com/articles/2009/07/06/up-and-running-with-cassandra/ where Evan Weaver writes: "Cassandra is an alpha product and could, theoretically, lose your data. In particular, if you change the schema specified in the storage-conf.xml file, you must follow these instructions carefully, or corruption will occur (this is going to be fixed). Also, the on-disk storage format is subject to change, making upgrading a bit difficult." Is database corruption a well-known or common problem with Cassandra? What sources of information would you recommend to help devise a strategy to minimize corruption risk, and to detect and recover when corruption does occur? Thanks, Hector Urroz --00c09f9235fe7e28bb0488926bc5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi all,

We're starting to prototype Cassandra for use in a prod= uction system and became concerned about data corruption after reading the = excellent article:
where Evan Weaver writes:

"Cassandra is an alpha= product and could, theoretically, lose your data. In particular, if you ch= ange the schema specified in the=A0storage-conf.xml=A0file, you must follow= =A0these instructions=A0carefully, or corruption will occur (this is going = to be fixed). Also, the on-disk storage format is subject to change, making= upgrading a bit difficult."

Is database corruption a well-known or common problem w= ith Cassandra? What sources of information would you recommend to help devi= se a strategy to minimize corruption risk, and to detect and recover when c= orruption does occur?

Thanks,

Hector Urroz

--00c09f9235fe7e28bb0488926bc5--