You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "vin01 (JIRA)" <ji...@apache.org> on 2016/06/19 12:21:05 UTC

[jira] [Updated] (CASSANDRA-12031) "LEAK DETECTED" during incremental repairs

     [ https://issues.apache.org/jira/browse/CASSANDRA-12031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

vin01 updated CASSANDRA-12031:
------------------------------
    Environment: Centos 6.6, x86_64, Cassandra 2.2.4  (was: Centos 6.6, x86_64)

> "LEAK DETECTED" during incremental repairs
> ------------------------------------------
>
>                 Key: CASSANDRA-12031
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12031
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Streaming and Messaging
>         Environment: Centos 6.6, x86_64, Cassandra 2.2.4
>            Reporter: vin01
>            Priority: Minor
>
> I encountered some errors during an incremental repair session which look like  :-
> ERROR [Reference-Reaper:1] 2016-06-19 03:28:35,884 Ref.java:187 - LEAK DETECTED: a reference (org.apache.cassandra.utils.concurrent.Ref$State@2ce0fab3) to class org.apache.cassandra.io.util.SafeMemory$MemoryTidy@1513857473:Memory@[7f2d462191f0..7f2d46219510) was not released before the reference was garbage collected
> Should i be worried about these? 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)