Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6F64D184AD for ; Wed, 25 Nov 2015 23:03:11 +0000 (UTC) Received: (qmail 16744 invoked by uid 500); 25 Nov 2015 23:03:11 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 16717 invoked by uid 500); 25 Nov 2015 23:03:11 -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 16706 invoked by uid 99); 25 Nov 2015 23:03:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Nov 2015 23:03:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id E687E2C1F56 for ; Wed, 25 Nov 2015 23:03:10 +0000 (UTC) Date: Wed, 25 Nov 2015 23:03:10 +0000 (UTC) From: "Ariel Weisberg (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-10688) Stack overflow from SSTableReader$InstanceTidier.runOnClose in Leak Detector MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-10688?page=3Dcom.atla= ssian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId= =3D15027758#comment-15027758 ]=20 Ariel Weisberg commented on CASSANDRA-10688: -------------------------------------------- It is just occurring to me, but if we just hit stack overflow what are the = odds that logging isn't also going to cause the stack to overflow? I mean i= n practice it doesn't seem to be happening, but it seems like it should! > Stack overflow from SSTableReader$InstanceTidier.runOnClose in Leak Detec= tor > -------------------------------------------------------------------------= --- > > Key: CASSANDRA-10688 > URL: https://issues.apache.org/jira/browse/CASSANDRA-1068= 8 > Project: Cassandra > Issue Type: Bug > Reporter: Jeremiah Jordan > Assignee: Ariel Weisberg > Fix For: 3.0.1, 3.1 > > > Running some tests against cassandra-3.0 9fc957cf3097e54ccd72e51b2d0650dc= 3e83eae0 > The tests are just running cassandra-stress write and read while adding a= nd removing nodes from the cluster. After the test runs when I go back thr= ough logs I find the following Stackoverflow fairly often: > ERROR [Strong-Reference-Leak-Detector:1] 2015-11-11 00:04:10,638 Ref.jav= a:413 - Stackoverflow [private java.lang.Runnable org.apache.cassandra.io.s= stable.format.SSTableReader$InstanceTidier.runOnClose, final java.lang.Runn= able org.apache.cassandra.io.sstable.format.SSTableReader$DropPageCache.and= Then, final org.apache.cassandra.cache.InstrumentingCache org.apache.cassan= dra.io.sstable.SSTableRewriter$InvalidateKeys.cache, private final org.apac= he.cassandra.cache.ICache org.apache.cassandra.cache.InstrumentingCache.map= , private final com.googlecode.concurrentlinkedhashmap.ConcurrentLinkedHash= Map org.apache.cassandra.cache.ConcurrentLinkedHashCache.map, final com.goo= glecode.concurrentlinkedhashmap.LinkedDeque com.googlecode.concurrentlinked= hashmap.ConcurrentLinkedHashMap.evictionDeque, com.googlecode.concurrentlin= kedhashmap.Linked com.googlecode.concurrentlinkedhashmap.LinkedDeque.first,= com.googlecode.concurrentlinkedhashmap.ConcurrentLinkedHashMap$Node com.go= oglecode.concurrentlinkedhashmap.ConcurrentLinkedHashMap$Node.next, com.goo= glecode.concurrentlinkedhashmap.ConcurrentLinkedHashMap$Node com.googlecode= .concurrentlinkedhashmap.ConcurrentLinkedHashMap$Node.next, com.googlecode.= concurrentlinkedhashmap.ConcurrentLinkedHashMap$Node com.googlecode.concurr= entlinkedhashmap.ConcurrentLinkedHashMap$Node.next, com.googlecode.concurre= ntlinkedhashmap.ConcurrentLinkedHashMap$Node com.googlecode.concurrentlinke= dhashmap.ConcurrentLinkedHashMap$Node.next, com.googlecode.concurrentlinked= hashmap.ConcurrentLinkedHashMap$Node com.googlecode.concurrentlinkedhashmap= .ConcurrentLinkedHashMap$Node.next, com.googlecode.concurrentlinkedhashmap.= ConcurrentLinkedHashMap$Node com.googlecode.concurrentlinkedhashmap.Concurr= entLinkedHashMap$Node.next, com.googlecode.concurrentlinkedhashmap.Concurre= ntLinkedHashMap$Node com.googlecode.concurrentlinkedhashmap.ConcurrentLinke= dHashMap$Node.next, com.googlecode.concurrentlinkedhashmap.ConcurrentLinked= HashMap$Node com.googlecode.concurrentlinkedhashmap.ConcurrentLinkedHashMap= $Node.next, com.googlecode.concurrentlinkedhashmap.ConcurrentLinkedHashMap$= Node com.googlecode.concurrentlinkedhashmap.ConcurrentLinkedHashMap$Node.ne= xt, com.googlecode.concurrentlinkedhashmap.ConcurrentLinkedHashMap$Node=20 > ....... (repeated a whole bunch more) ....=20 > com.googlecode.concurrentlinkedhashmap.ConcurrentLinkedHashMap$Node com.g= ooglecode.concurrentlinkedhashmap.ConcurrentLinkedHashMap$Node.next, com.go= oglecode.concurrentlinkedhashmap.ConcurrentLinkedHashMap$Node com.googlecod= e.concurrentlinkedhashmap.ConcurrentLinkedHashMap$Node.next, com.googlecode= .concurrentlinkedhashmap.ConcurrentLinkedHashMap$Node com.googlecode.concur= rentlinkedhashmap.ConcurrentLinkedHashMap$Node.next, com.googlecode.concurr= entlinkedhashmap.ConcurrentLinkedHashMap$Node com.googlecode.concurrentlink= edhashmap.ConcurrentLinkedHashMap$Node.next, com.googlecode.concurrentlinke= dhashmap.ConcurrentLinkedHashMap$Node com.googlecode.concurrentlinkedhashma= p.ConcurrentLinkedHashMap$Node.next, final java.lang.Object com.googlecode.= concurrentlinkedhashmap.ConcurrentLinkedHashMap$Node.key, public final byte= [] org.apache.cassandra.cache.KeyCacheKey.key -- This message was sent by Atlassian JIRA (v6.3.4#6332)