[
https://issues.apache.org/jira/browse/CASSANDRA-6572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14070368#comment-14070368
]
Lyuben Todorov commented on CASSANDRA-6572:
-------------------------------------------
Added thread id to the logs in
[b2c4503|https://github.com/lyubent/cassandra/commit/b2c45034fe9a3b75f35ac9052aa177931cda1879],
planning on changing the {{Iterable<QeuryLogSegment>}} to {{Map<Integer,
Iterable<QeuryLogSegment>>}} so that each entry represents a single thread's
collection of querylog segments (with the integer being the thread id as
recorded in the logs) and then submitting each iterable as a runnable task to
an executor service.
The one thing I struggled finding is session information, we have access to new
connections in {{o.a.c.transport.Server#ConnectionTracker#addConnection}} but
beyond that I didn't see where session information could be accessed.
> 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: Lyuben Todorov
> 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.2#6252)
