Jonathan Ellis created CASSANDRA-4862:
-----------------------------------------
Summary: Include session information in tracing activity output
Key: CASSANDRA-4862
URL: https://issues.apache.org/jira/browse/CASSANDRA-4862
Project: Cassandra
Issue Type: Improvement
Components: Core
Affects Versions: 1.2.0 beta 1
Reporter: Jonathan Ellis
Assignee: Aleksey Yeschenko
Fix For: 1.2.0 beta 2
Would like something like this:
activity | timestamp | source | source_elapsed
-------------------------------------+--------------+-----------+----------------
execute_cql3_query | 09:57:27,290 | 127.0.0.1 | 0
Determining replicas for mutation | 09:57:27,290 | 127.0.0.1 | 2465
Sending message to /127.0.0.2 | 09:57:27,294 | 127.0.0.1 | 7105
Messsage received from /127.0.0.1 | 09:57:27,296 | 127.0.0.2 | 62
Applying mutation | 09:57:27,298 | 127.0.0.2 | 1246
Acquiring switchLock | 09:57:27,298 | 127.0.0.2 | 1353
Appending to commitlog | 09:57:27,298 | 127.0.0.2 | 1378
Adding to memtable | 09:57:27,298 | 127.0.0.2 | 1439
Enqueuing response to /127.0.0.1 | 09:57:27,298 | 127.0.0.2 | 1892
Messsage received from /127.0.0.2 | 09:57:27,301 | 127.0.0.1 | 14493
Sending message to /127.0.0.1 | 09:57:27,301 | 127.0.0.2 | 4527
Processing response from /127.0.0.2 | 09:57:27,302 | 127.0.0.1 | 15072
Request complete | 09:57:27,302 | 127.0.0.1 | 15100
{noformat}
... where first and last lines are coming from the sessions table.
Note that currently session table records started_at and finished_at; this will
require also recording duration from the stopwatch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
