cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Olsson (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-11215) Reference leak with parallel repairs on the same table
Date Tue, 23 Feb 2016 14:24:18 GMT
Marcus Olsson created CASSANDRA-11215:

             Summary: Reference leak with parallel repairs on the same table
                 Key: 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
ERROR [Reference-Reaper:1] 2016-02-23 15:02:05,516 - LEAK DETECTED: a reference
(org.apache.cassandra.utils.concurrent.Ref$State@5213f926) to class
was not released before the reference was garbage collected

Reproducible with:
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

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

View raw message