You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Joshua McKenzie (JIRA)" <ji...@apache.org> on 2015/09/22 20:23:05 UTC

[jira] [Updated] (CASSANDRA-9918) Introduce extra Ref usage when debugrefcount=true

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

Joshua McKenzie updated CASSANDRA-9918:
---------------------------------------
    Fix Version/s:     (was: 3.0.0 rc2)
                   3.x

> Introduce extra Ref usage when debugrefcount=true
> -------------------------------------------------
>
>                 Key: CASSANDRA-9918
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9918
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Benedict
>            Assignee: Benedict
>             Fix For: 3.x
>
>
> To help us in testing catch API misuse, especially resource handling, we can introduce an abstract base class implementing AutoCloseable that under normal circumstances is empty, but when ref count debugging is enabled instantiates a Ref instance that it releases on close. This will let us detect objects we are misusing that we consider too high-traffic for normal systems to have tracked by Refs. Ideally CASSANDRA-9379 will be delivered around the same time, so that this can be enabled on live systems without _much_ negative impact.



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