You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2014/07/28 19:20:38 UTC
[jira] [Commented] (CASSANDRA-7629) tracing no longer logs when the
request completed
[ https://issues.apache.org/jira/browse/CASSANDRA-7629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14076416#comment-14076416 ]
Jonathan Ellis commented on CASSANDRA-7629:
-------------------------------------------
I think you're mis-remembering. The only "request complete" in 2.0 is a debug log entry, which is still there in 2.1:
{code}
public void stopSession()
{
TraceState state = this.state.get();
if (state == null) // inline isTracing to avoid implicit two calls to state.get()
{
logger.debug("request complete");
}
{code}
> tracing no longer logs when the request completed
> -------------------------------------------------
>
> Key: CASSANDRA-7629
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7629
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Brandon Williams
> Fix For: 2.1.1
>
>
> In 2.0 and before, there is a "Request complete" entry in tracing, which no longer appears in 2.1. This makes it difficult to reason about latency/performance problems in a trace.
--
This message was sent by Atlassian JIRA
(v6.2#6252)