[ https://issues.apache.org/jira/browse/CASSANDRA-9226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14507677#comment-14507677 ]
Vishy Kasar commented on CASSANDRA-9226: ---------------------------------------- Sorry wrong project. This was meant to be a driver enhancement request. Will raise it there. > Log streamid at the trace level on sending request and receiving response > ------------------------------------------------------------------------- > > Key: CASSANDRA-9226 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9226 > Project: Cassandra > Issue Type: Improvement > Components: Core > Reporter: Vishy Kasar > > Multiple requests are sent on the same connection and responses arrive in any > order. It is hard to track single request/response pair even when the trace > logs are turned on today because the trace logs only provide information up > to connection as shown below. It will be super useful to also provide the > streamid in the trace logs. > 2015/04/17 14:02:43.334 TRACE [New I/O worker #447] > com.datastax.driver.core.Connection - > Connection[host1.domain.com/10.0.1.1:9042-1, inFlight=1, closed=false] > request sent successfully > 2015/04/17 14:02:43.337 TRACE [New I/O worker #447] > com.datastax.driver.core.Connection - > Connection[host1.domain.com/10.0.1.1:9042-1, inFlight=1, closed=false] > received: ROWS [column1 (timeuuid)][value (blob)][writetime(value) (bigint)] > streamid will be useful at-least in the 2 logs above. But if you know of > other cases where it will be useful, please add it there as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)