Databases
StackOverflow2013
Postsdbo
POGetting OutOfMemory in Cassandra Java Heap Space version 1.0.7 frequently on different nodes
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGetting OutOfMemory in Cassandra Java Heap Space version 1.0.7 frequently on different nodes
    primarykey
    data
    text
    <p>I am running Cassandra 1.0.7, 5 nodes, each node has 8GB physical RAM, and my heap is 4GB. Frequently I have started getting node failures like this:</p> <pre><code> WARN [ScheduledTasks:1] 2013-04-10 10:18:12,042 GCInspector.java (line 145) Heap is 0.9602098156121341 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 WARN [ScheduledTasks:1] 2013-04-10 10:18:12,042 StorageService.java (line 2645) Flushing CFS(Keyspace='Company', ColumnFamily='01_Meta') to relieve memory pressure WARN [ScheduledTasks:1] 2013-04-10 10:18:14,403 GCInspector.java (line 145) Heap is 0.9610030442856479 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 WARN [ScheduledTasks:1] 2013-04-10 10:18:14,403 StorageService.java (line 2645) Flushing CFS(Keyspace='Company', ColumnFamily='01_Meta') to relieve memory pressure ERROR [MutationStage:23969] 2013-04-10 10:18:18,339 AbstractCassandraDaemon.java (line 139) Fatal exception in thread Thread[MutationStage:23969,5,main] java.lang.OutOfMemoryError: Java heap space at java.nio.HeapByteBuffer.&lt;init&gt;(HeapByteBuffer.java:39) at java.nio.ByteBuffer.allocate(ByteBuffer.java:312) at org.apache.cassandra.utils.SlabAllocator.allocate(SlabAllocator.java:68) at org.apache.cassandra.utils.Allocator.clone(Allocator.java:32) at org.apache.cassandra.db.Column.localCopy(Column.java:244) at org.apache.cassandra.db.Memtable.resolve(Memtable.java:215) at org.apache.cassandra.db.Memtable.put(Memtable.java:143) at org.apache.cassandra.db.ColumnFamilyStore.apply(ColumnFamilyStore.java:805) at org.apache.cassandra.db.Table.apply(Table.java:431) at org.apache.cassandra.db.RowMutation.apply(RowMutation.java:256) at org.apache.cassandra.service.StorageProxy$6.runMayThrow(StorageProxy.java:416) at org.apache.cassandra.service.StorageProxy$DroppableRunnable.run(StorageProxy.java:1223) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) </code></pre> <p>The startup parameters are:</p> <pre><code>/usr/lib/jvm/jdk1.6.0_31/bin/java -ea -javaagent:/usr/share/cassandra//lib/jamm-0.2.5.jar -XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42 -Xms4G -Xmx4G heap size -Xmn200M -XX:+HeapDumpOnOutOfMemoryError -Xss128k -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:SurvivorRatio=8 -XX:MaxTenuringThreshold=1 -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -Djava.net.preferIPv4Stack=true -Dcom.sun.management.jmxremote.port=7199 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Dlog4j.configuration=log4j-server.properties -Dlog4j.defaultInitOverride=true -Dcassandra-pidfile=/var/run/cassandra/cassandra.pid -cp /etc/cassandra/conf:/usr/share/cassandra/lib/antlr- </code></pre> <p>Any ideas on where to start? I was looking here: <a href="http://www.datastax.com/docs/1.0/operations/tuning#tuning-options-for-size-tiered-compaction" rel="nofollow">http://www.datastax.com/docs/1.0/operations/tuning#tuning-options-for-size-tiered-compaction</a> <a href="http://www.datastax.com/docs/1.0/operations/tuning#tuning-java-heap-size" rel="nofollow">http://www.datastax.com/docs/1.0/operations/tuning#tuning-java-heap-size</a></p> <p>But so far nothing seems out of the ordinary. Any suggestions greatly appreciated.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USrobert towne
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POGetting OutOfMemory in Cassandra Java Heap Space version 1.0.7 frequently on different nodes
      1. This table or related slice is empty.
      1. VTDownMod
    2. VO
      singulars
      1. POGetting OutOfMemory in Cassandra Java Heap Space version 1.0.7 frequently on different nodes
      1. This table or related slice is empty.
      1. VTDownMod
    3. VO
      singulars
      1. POGetting OutOfMemory in Cassandra Java Heap Space version 1.0.7 frequently on different nodes
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload