Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cassandra-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of rrabah@playdom.com designates
 74.125.149.71 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1258755032.4068.30.camel@btoddb-laptop>
References: <e06563880911201317i73c247c8ude7a68fbcdade127@mail.gmail.com>
	 <1258755032.4068.30.camel@btoddb-laptop>
Date: Fri, 20 Nov 2009 14:34:01 -0800
Message-ID: <a1625f290911201434h29ba2afx272ae6b5c9624ea9@mail.gmail.com>
Subject: Re: Cassandra users survey
From: Ramzi Rabah <rrabah@playdom.com>
To: cassandra-user@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

We are currently evaluating Cassandra, and using it for a small
feature in production. We are only using the basic insert/get/remove
from the API, with a standard column family. So far, I like a lot of
what Cassandra offers, though I had some tough times with it.

* Version 0.4.2 seems very broken. Besides CASSANDRA-507 which is not
fixed in the v4 version, it seems that when you do significant amount
of deletes, and you try to restart the server, compaction fails pretty
much most of the time in our environment.
* Version 0.5 seems to be better in terms of stability from what I
observed so far. Some things that would definitely be very helpful for
us going forward:
- Easier way to replace a node that dies.
- Disk is not infinite so a way to say when you insert an entry into
cassandra, how long do you want it to be available before it is
deleted by Cassandra.
- Better monitoring tools. It's very hard to tell how heavily loaded a
node and the whole system is right now.