Thanks Aaron for the indormation.
I increased the VM size to 2.4G from 1.4G. Please check my current CF in
below.
Keyspace: WCache:
Replication Strategy: org.apache.cassandra.locator.SimpleStrategy
Durable Writes: true
Options: [replication_factor:3]
Column Families:
ColumnFamily: W
> flush_largest_memtables_at
Is designed as a safety valve, reducing it may help prevent an oom but it wont
get to the cause.
Assuming you cannot just allocate more memory to the JVM, and you are running
the default settings in cassandra-env.sh (other than the changes mentioned),
and you are o
Hi Experts
Under massive write load what would be the best value for Cassandra *
flush_largest_memtables_at* setting? Yesterday I got an OOM exception in
one of our production Cassandra node under heavy write load within 5 minute
duration.
I change the above setting value to .45 and also change t
