[
https://issues.apache.org/jira/browse/CASSANDRA-6572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14153974#comment-14153974
]
Carl Yeksigian commented on CASSANDRA-6572:
-------------------------------------------
I have a rebase of the branch
[here|https://github.com/carlyeks/cassandra/tree/6572], but haven't yet gotten
around to fixing the issues pointed out.
Overall, though, I'm not sure what we are trying to accomplish with these
additions that can't already be accomplished with the new stress tool,
especially since this will be sampling, and might not even be running when the
event that you wanted to replay took place.
If we are using this to replicate workloads for replaying a workload, then the
new stress tool can be better configured to do that. With the sampling, the
workload wouldn't be the same as it was when we were capturing it, so we won't
be able to replicate it exactly.
If there is a specific query that is failing, trying to reproduce it and pull
together a workload replay is probably going to involve steps similar to
putting together a stress profile.
One other thing about using a stress profile instead of a workload replay is
that it would be more open for people to use, since it wouldn't include any
sensitive information.
I can continue moving this forward, but I'm skeptical about it being enough of
a benefit for the additional risk it entails versus the stress tool we already
have.
> Workload recording / playback
> -----------------------------
>
> Key: CASSANDRA-6572
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6572
> Project: Cassandra
> Issue Type: New Feature
> Components: Core, Tools
> Reporter: Jonathan Ellis
> Assignee: Carl Yeksigian
> Fix For: 2.1.1
>
> Attachments: 6572-trunk.diff
>
>
> "Write sample mode" gets us part way to testing new versions against a real
> world workload, but we need an easy way to test the query side as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
