[
https://issues.apache.org/jira/browse/CASSANDRA-12031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15364071#comment-15364071
]
Sylvain Lebresne commented on CASSANDRA-12031:
--
The message says that we hadn't released some memory that we should have, which
is a bug, but the presence of the message imply said memory has just been
freed, so no, you shouldn't be worried too much.
Of course, we should still fix this. But there has been a few fix related to
leaked references recently, so I would suggest upgrading to 2.2.7 (which has
just been voted on successfully so should be available later today or tomorrow)
and see if you can reproduce there. If you can, maybe some additional log
context for the error message could help track this down.
> "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)
