Marcus Olsson created CASSANDRA-11215:
-----------------------------------------
Summary: Reference leak with parallel repairs on the same table
Key: CASSANDRA-11215
URL: https://issues.apache.org/jira/browse/CASSANDRA-11215
Project: Cassandra
Issue Type: Bug
Reporter: Marcus Olsson
Assignee: Marcus Olsson
When starting multiple repairs on the same table Cassandra starts to log about
reference leak as:
{noformat}
ERROR [Reference-Reaper:1] 2016-02-23 15:02:05,516 Ref.java:187 - LEAK
DETECTED: a reference
(org.apache.cassandra.utils.concurrent.Ref$State@5213f926) to class
org.apache.cassandra.io.sstable.format.SSTableReader
$InstanceTidier@605893242:.../testrepair/standard1-dcf311a0da3411e5a5c0c1a39c091431/la-30-big
was not released before the reference was garbage collected
{noformat}
Reproducible with:
{noformat}
ccm create repairtest -v 2.2.5 -n 3
ccm start
ccm stress write n=1000000 -schema
replication(strategy=SimpleStrategy,factor=3) keyspace=testrepair
# And then perform two repairs concurrently with:
ccm node1 nodetool repair testrepair
{noformat}
I know that starting multiple repairs in parallel on the same table isn't very
wise, but this shouldn't result in reference leaks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
