incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <jbel...@gmail.com>
Subject Re: Cassndra 1.0.6 GC query
Date Mon, 27 Feb 2012 22:04:09 GMT
Take a heap dump (there should be one from when you OOMed) and see
what is consuming your memory.

On Mon, Feb 27, 2012 at 3:45 PM, Roshan <codevally@gmail.com> wrote:
> Hi Experts
>
> After getting an OOM error in production, I reduce the
> -XX:CMSInitiatingOccupancyFraction to .45 (from .75) and
> flush_largest_memtables_at to .45 (from .75). But still I am get an warning
> message in production for the same Cassandra node regarding OOM. Also reduce
> the concurrent compactions to one.
>
> 2012-02-27 08:01:12,913 WARN  [GCInspector] Heap is 0.45604122065696395
> full.  You may need to reduce memtable and/or cache sizes.  Cassandra will
> now flush up to the two largest memtables to free up memory.  Adjust
> flush_largest_memtables_at threshold in cassandra.yaml if you don't want
> Cassandra to do this automatically
> 2012-02-27 08:01:12,913 WARN  [StorageService] Flushing
> CFS(Keyspace='WCache', ColumnFamily='WStandard') to relieve memory pressure
>
> Could someone please explain why still I am getting GC warnings like above.
> Many thanks.
>
> --
> View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Cassndra-1-0-6-GC-query-tp7323457p7323457.html
> Sent from the cassandra-user@incubator.apache.org mailing list archive at Nabble.com.



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

Mime
View raw message