Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 29 Jul 2015 15:06:04 +0000 (UTC)
From: "Benedict (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12849952.1438182346000.319695.1438182364542@Atlassian.JIRA>
In-Reply-To: <JIRA.12849952.1438182346000@Atlassian.JIRA>
References: <JIRA.12849952.1438182346000@Atlassian.JIRA>
 <JIRA.12849952.1438182346547@arcas>
Subject: [jira] [Created] (CASSANDRA-9918) Introduce extra Ref usage when
 debugrefcount=true
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Benedict created CASSANDRA-9918:
-----------------------------------

             Summary: 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.0.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)