cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7629) tracing no longer logs when the request completed
Date Tue, 29 Jul 2014 22:27:39 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14078510#comment-14078510
] 

Brandon Williams commented on CASSANDRA-7629:
---------------------------------------------

So, we don't have an actual event for this since cqlsh is sort of faking it, but I think we
should, because when you select from system_traces manually you don't have this information,
which can be critical in many circumstances.

> 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
>            Assignee: Tyler Hobbs
>            Priority: Minor
>             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)

Mime
View raw message