Return-Path: Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: (qmail 8057 invoked from network); 2 Jul 2010 17:12:15 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 2 Jul 2010 17:12:15 -0000 Received: (qmail 29691 invoked by uid 500); 2 Jul 2010 17:12:15 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 29627 invoked by uid 500); 2 Jul 2010 17:12:15 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 29619 invoked by uid 99); 2 Jul 2010 17:12:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Jul 2010 17:12:14 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Jul 2010 17:12:12 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o62HBpMC011689 for ; Fri, 2 Jul 2010 17:11:51 GMT Message-ID: <7202695.176901278090711084.JavaMail.jira@thor> Date: Fri, 2 Jul 2010 13:11:51 -0400 (EDT) From: "Jonathan Ellis (JIRA)" To: commits@cassandra.apache.org Subject: [jira] Resolved: (CASSANDRA-1177) OutOfMemory on heavy inserts In-Reply-To: <22280981.3361276095853112.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/CASSANDRA-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis resolved CASSANDRA-1177. --------------------------------------- Resolution: Duplicate CASSANDRA-685 and CASSANDRA-981 will address this in 0.7. For 0.6 the best solution is to throttle writes if you start seeing TimedOutExceptions. > OutOfMemory on heavy inserts > ---------------------------- > > Key: CASSANDRA-1177 > URL: https://issues.apache.org/jira/browse/CASSANDRA-1177 > Project: Cassandra > Issue Type: Bug > Components: Core > Affects Versions: 0.6.2 > Environment: SunOS 5.10, x86 32bit, Jave Hotspot Server VM 11.2-b01 mixed mode > Sun SDK 1.6.0_12-b04 > Reporter: Torsten Curdt > Priority: Critical > Attachments: bug report.zip, commitlog.txt, data.txt > > > 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.