cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Frisch, Michael" <Michael.Fri...@nuance.com>
Subject Re: Leak detected during repair (v2.1.8)
Date Fri, 31 Jul 2015 15:20:16 GMT
This is not the case; I built and deployed the latest code from the 2.1.x branch in Github
and the issue still exists.

- Mike

From: Jeff Jirsa <Jeff.Jirsa@crowdstrike.com<mailto:Jeff.Jirsa@crowdstrike.com>>
Reply-To: Cassandra List <user@cassandra.apache.org<mailto:user@cassandra.apache.org>>
Date: Wednesday, July 29, 2015 at 12:07 PM
To: Cassandra List <user@cassandra.apache.org<mailto:user@cassandra.apache.org>>
Subject: Re: Leak detected during repair (v2.1.8)

https://issues.apache.org/jira/browse/CASSANDRA-9382


From: "Frisch, Michael"
Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
Date: Wednesday, July 29, 2015 at 6:56 AM
To: Cassandra List
Subject: Leak detected during repair (v2.1.8)


ERROR [Reference-Reaper:1] 2015-07-29 12:34:45,941 Ref.java:179 - LEAK DETECTED: a reference
(org.apache.cassandra.utils.concurrent.Ref$State@52628658) to class org.apache.cassandra.io.sstable.SSTableReader$InstanceTidier@1113728425:/data/cassandra/data/KSName/CFName/snapshots/8179b820-35ec-11e5-a75f-ed9e19db78e9/KSName-CFName-ka-5544
was not released before the reference was garbage collected

ERROR [Reference-Reaper:1] 2015-07-29 12:34:45,948 Ref.java:179 - LEAK DETECTED: a reference
(org.apache.cassandra.utils.concurrent.Ref$State@4eef1d76) to class org.apache.cassandra.io.sstable.SSTableReader$InstanceTidier@880236150:/data/cassandra/data/KSName/CFName/snapshots/8179b820-35ec-11e5-a75f-ed9e19db78e9/KSName-CFName-ka-5543
was not released before the reference was garbage collected

I was just wondering if this is a known issue or if others are experiencing this with C* v2.1.8.
 I couldn't find any open tickets in the Jira about these leaks occurring during repairs.
 I've only seen this during repairs and the only commonality that I could find between the
column families that these leaks have been repeated for is that they contain very little data.
 Could there be a race condition that's only hit when repairing very small datasets?  Turning
on debug logging didn't produce any more context like I had hoped for.

Regards,
- Mike

Mime
View raw message