cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-9423) Improve Leak Detection to cover strong reference leaks
Date Fri, 26 Jun 2015 11:57:04 GMT

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

Benedict updated CASSANDRA-9423:
--------------------------------
    Fix Version/s:     (was: 3.0.x)
                   2.1.8

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

Mime
View raw message