Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 93282 invoked from network); 15 Dec 2010 11:02:30 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 15 Dec 2010 11:02:30 -0000 Received: (qmail 74749 invoked by uid 500); 15 Dec 2010 11:02:28 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 74438 invoked by uid 500); 15 Dec 2010 11:02:27 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 74430 invoked by uid 99); 15 Dec 2010 11:02:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Dec 2010 11:02:27 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [212.14.72.4] (HELO mail.berlin01.toptarif.de) (212.14.72.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Dec 2010 11:02:20 +0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1082) Subject: Re: Memory leak with Sun Java 1.6 ? From: Timo Nentwig In-Reply-To: <56F54377-E3B5-4E4D-9478-0B4F46E2104A@toptarif.de> Date: Wed, 15 Dec 2010 12:01:52 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <240C5ACB-6A82-4DD4-8CD9-6423767F082A@toptarif.de> References: <43B93B23-D289-481A-8C69-8BCB866ADFF9@toptarif.de> <2E5D89FA-274D-4811-8EE5-BD389FB0E015@toptarif.de> <7F6C35CA-70C0-456E-AB9D-9DC883576DC1@toptarif.de> <560C1FD8-6997-45F9-A8AE-98431CFB5DF7@toptarif.de> <56F54377-E3B5-4E4D-9478-0B4F46E2104A@toptarif.de> To: user@cassandra.apache.org X-Mailer: Apple Mail (2.1082) On Dec 14, 2010, at 23:23, Timo Nentwig wrote: > On Dec 14, 2010, at 21:07, Peter Schuller wrote: >=20 >> In that case, based on the strack trace, I wonder if you're hitting >> what I was hitting just yesterday/earlier today: >>=20 >> https://issues.apache.org/jira/browse/CASSANDRA-1860 >>=20 >> Which is suspected (currently being tested that it's gone with = updated >> 0.7) to be due to: >>=20 >> https://issues.apache.org/jira/browse/CASSANDRA-1847 >>=20 >> If the corruption happens to be slightly different in your case, = maybe >> it just ends up trying to allocate a large array instead of the >> failure mode I got (EOF or bad cfId) on the receiving end. >>=20 >> Can you try to reproduce with the latest 0.7 branch as of today? >=20 > I'll try to do so tomorrow. So I git'ed 0.7.0-rc2-SNAPSHOT 9:30 UTC+2 and this one indeed seems to = run much more stable (still disk_access: standard), no problems to far = (runs roughly for half an hour, 7.5M INSERTs, running nodetool cleanup = concurrently on one node). And it's also significantly faster/back to = usual speed. Hooray! :) When is rc3 going to be released? Thanks for the support!=