Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-11215

Reference leak with parallel repairs on the same table

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • 2.2.6, 3.0.5, 3.5
    • None
    • None
    • Normal

    Description

      When starting multiple repairs on the same table Cassandra starts to log about reference leak as:

      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
      

      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.

      Attachments

        Issue Links

          Activity

            People

              molsson Marcus Olsson
              molsson Marcus Olsson
              Marcus Olsson
              Marcus Eriksson
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: