cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-12031) "LEAK DETECTED" during incremental repairs
Date Wed, 03 Aug 2016 12:42:20 GMT

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

Paulo Motta updated CASSANDRA-12031:
------------------------------------
    Resolution: Cannot Reproduce
        Status: Resolved  (was: Awaiting Feedback)

Closing this as cannot reproduce for now. Please reopen if reproducible in newer versions.

> "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)

Mime
View raw message