[
https://issues.apache.org/jira/browse/CASSANDRA-9423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14602797#comment-14602797
]
Aleksey Yeschenko commented on CASSANDRA-9423:
----------------------------------------------
The fixes should to into 2.1.8 (and as a separate ticket, really).
No objections to putting the improved detection into 2.1, if it truly doesn't
affect the system unless enabled explicitly (which seems to be the case from a
quick glance at the patch). No strong feelings though, given that 2.1 will be
EOL very soon. Must to at least into 2.2 though.
> Improve Leak Detection to cover strong reference leaks
> ------------------------------------------------------
>
> Key: CASSANDRA-9423
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9423
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Benedict
> Priority: Critical
> Fix For: 2.1.8
>
>
> Currently we detect resources that we don't cleanup that become unreachable.
> We could also detect references that appear to have leaked without becoming
> unreachable, by periodically scanning the set of extant refs, and checking if
> they are reachable via their normal means (if any); if their lifetime is
> unexpectedly long this likely indicates a problem, and we can log a
> warning/error.
> Assigning to myself to not forget it, since this may well help especially
> with [~tjake]'s concerns highlighted on 8099 for 3.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
