cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Stupp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9479) Improve trace messages
Date Tue, 26 May 2015 17:13:18 GMT

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

Robert Stupp commented on CASSANDRA-9479:
-----------------------------------------

Unfortunately it's not clear (to me).

I've got a trace for a {{SELECT foo FROM bar LIMIT 100}} using CL {{LOCAL_QUORUM}}.

The trace tells about the distribution of the read requests and the answers to the reads.
But immediately after each received read response, the coordinator issues row mutations to
the nodes - and AFAIK it could theoretically be a {{READ_REPAIR}} or a simple {{MUTATION}}
- both can result in {{Acquiring switchLock read lock}}. (C* 2.0.11)

> Improve trace messages
> ----------------------
>
>                 Key: CASSANDRA-9479
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9479
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Robert Stupp
>            Priority: Minor
>
> Currently, tracing only records lines like
> {{Enqueuing response to}} / {{Processing response from}} or
> {{Sending message to}} / {{Message received from}}.
> It would help if these messages also contain some information about the verb and (if
easily accessible) about kind of content.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message