cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <jbel...@gmail.com>
Subject Re: OOM during batch_mutate
Date Tue, 08 Feb 2011 16:50:57 GMT
No, on 0.6 copying settings for a 32GB machine to a 16GB machine would
also be a great way to OOM.  The difference is that you had to set
memtable thresholds globally in the xml file in 0.6, instead of being
able to do it per-columnfamily from the cli.

On Tue, Feb 8, 2011 at 10:40 AM, Chris Burroughs
<chris.burroughs@gmail.com> wrote:
> On 02/07/2011 06:05 PM, Jonathan Ellis wrote:
>> Sounds like the keyspace was created on the 32GB machine, so it
>> guessed memtable sizes that are too large when run on the 16GB one.
>> Use "update column family" from the cli to cut the throughput and
>> operations thresholds in half, or to 1/4 to be cautious.
>
>
> This guessing is new in 0.7.x right?  On a 0.6.x storage-conf.xml +
> sstables can be moved among machines with different amounts of RAM
> without needing to change anything through the cli?
>
>



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

Mime
View raw message