cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roshan <>
Subject Re: Best suitable value for flush_largest_memtables_at
Date Thu, 23 Feb 2012 21:30:05 GMT
Thanks Aaron for the indormation.

I increased the VM size to 2.4G from 1.4G. Please check my current CF in

Keyspace: WCache:
  Replication Strategy: org.apache.cassandra.locator.SimpleStrategy
  Durable Writes: true
    Options: [replication_factor:3]
  Column Families:
    ColumnFamily: WStandard
      Key Validation Class: org.apache.cassandra.db.marshal.BytesType
      Default column value validator:
      Columns sorted by: org.apache.cassandra.db.marshal.BytesType
      Row cache size / save period in seconds / keys to save : 1000.0/0/all
      Row Cache Provider:
      Key cache size / save period in seconds: 200001.0/3600
      GC grace seconds: 3600
      Compaction min/max thresholds: 4/32
      Read repair chance: 1.0
      Replicate on write: true
      Built indexes: []
      Compaction Strategy:

I have already done the below configuration changes after getting the OOM.

JVM_OPTS -XX:CMSInitiatingOccupancyFraction=45 (reduce it from 75)

flush_largest_memtables_at: 0.45 (reduce it from .75)
reduce_cache_sizes_at: 0.55 (reduce it from .85)
reduce_cache_capacity_to: 0.3 (reduce it from .6)
concurrent_compactors: 1

I will also apply the configuration you suggest in locally first then to
production. Appreciate your comments regarding this. Thanks. 

View this message in context:
Sent from the mailing list archive at

View raw message