Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 3 Aug 2015 22:07:04 +0000 (UTC)
From: "Jeremy Hanna (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12851229.1438639600000.360538.1438639624632@Atlassian.JIRA>
In-Reply-To: <JIRA.12851229.1438639600000@Atlassian.JIRA>
References: <JIRA.12851229.1438639600000@Atlassian.JIRA>
 <JIRA.12851229.1438639600359@arcas>
Subject: [jira] [Created] (CASSANDRA-9969) Expose the DTCS configuration
 parameters (base time, min threshold, max age) via jmx
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Jeremy Hanna created CASSANDRA-9969:
---------------------------------------

             Summary: Expose the DTCS configuration parameters (base time, min threshold, max age) via jmx
                 Key: CASSANDRA-9969
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9969
             Project: Cassandra
          Issue Type: Improvement
            Reporter: Jeremy Hanna


The DateTieredCompactionStrategy settings aren't exposed via JMX.  There are a few use cases for which this would be valuable.

1. Testing via write survey mode.  Currently you can change the compaction strategy class but are limited to change min/max compaction threshold.
2. Testing via trying out the strategy on one node in your existing cluster.  This helps you to understand the impact when transitioning from another compaction strategy to DTCS.
3. Transitioning your cluster to DTCS one node at a time for minimal impact (then of course changing the persisted schema).

This should go back to 2.0 or at least 2.1 because it's really a simple oversight to not have exposed those in ColumnFamilyStoreMBean.


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