Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Sun, 8 Mar 2015 13:53:39 +0000 (UTC)
From: "Robert Stupp (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12780103.1425657473000.31598.1425822819121@Atlassian.JIRA>
In-Reply-To: <JIRA.12780103.1425657473000@Atlassian.JIRA>
References: <JIRA.12780103.1425657473000@Atlassian.JIRA>
 <JIRA.12780103.1425657473058@arcas>
Subject: [jira] [Commented] (CASSANDRA-8929) Workload sampling
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-8929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352050#comment-14352050 ] 

Robert Stupp commented on CASSANDRA-8929:
-----------------------------------------

Should we try to target this for 2.1.x, if it is not too intrusive?

> Workload sampling
> -----------------
>
>                 Key: CASSANDRA-8929
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8929
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tools
>            Reporter: Jonathan Ellis
>
> Workload *recording* looks to be unworkable (CASSANDRA-6572).  We could build something almost as useful by sampling the requests sent to a node and building a synthetic workload with the same characteristics using the same (or anonymized) schema.


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