[CASSANDRA-1177] OutOfMemory on heavy inserts

• Type: Bug
• Status: Resolved
• Priority: Urgent
• Resolution: Duplicate

Environment

SunOS 5.10, x86 32bit, Jave Hotspot Server VM 11.2-b01 mixed mode
Sun SDK 1.6.0_12-b04

• Severity: Critical
• Assignee: Unassigned
• Reporter: Torsten Curdt
• Created: 09/Jun/10 15:03
• Updated: 16/Apr/19 09:33
• Resolved: 02/Jul/10 17:11

Description

We have cluster of 6 Cassandra 0.6.2 nodes running under SunOS (see environment).

On initial import (using the thrift API) we see some weird behavior of half the cluster. While cas04-06 look fine as you can see from the attached munin graphs, the other 3 nodes kept on GCing (see log file) until they became unreachable and went OOM. (This is also why the stats are so spotty - munin could no longer reach the boxes) We have seen the same behavior on 0.6.2 and 0.6.1. This started after around 100 million inserts.

Looking at the hprof (which is of course to big to attach) we see lots of ConcurrentSkipListMap$Node's and quite some Column objects. Please see the stats attached.

This looks similar to https://issues.apache.org/jira/browse/CASSANDRA-1014 but we are not sure it really is the same.

Issue Links

• relates to: CASSANDRA-1014 GC storming, possible memory leak