cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <jbel...@gmail.com>
Subject Re: Experiences with Cassandra hardware planning
Date Mon, 25 Oct 2010 16:07:25 GMT
On Mon, Oct 25, 2010 at 10:25 AM, Edward Capriolo <edlinuxguru@gmail.com> wrote:
>> 2. We gave up on using Cassandra's row cache as loading any reasonable
>> amount of data into the cache would take days/weeks with our tiny row size.
>>  We instead are using file system cache.

I don't follow the reasoning there.  Row cache or fs cache, it will be
hot after reading it once, the difference is that doing a read to the
cached data is much faster from row cache.

>> 4. When Cassandra is set to replication factor of three and the read replica
>> count is one, data still gets read (for read repair) on all three nodes that
>> have a copy of the data.

FWIW, you don't have to wait for 0.7 to turn this off (see
http://www.riptano.com/blog/whats-new-cassandra-066).  However, to pin
affinity to a single replica you will need SimpleStrategy from 0.7.

-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com

Mime
View raw message