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] [Resolved] (CASSANDRA-11112) Tracing should denote when a request is sent due to speculative retry
Date Tue, 02 Feb 2016 22:11:39 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-11112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brandon Williams resolved CASSANDRA-11112.
------------------------------------------
    Resolution: Implemented

I missed this:
{noformat}
 speculating read retry on /10.208.8.123 [SharedPool-Worker-1] | 2016-02-02 22:09:23.017000
| 10.208.8.63 |          10079
{noformat}

> Tracing should denote when a request is sent due to speculative retry
> ---------------------------------------------------------------------
>
>                 Key: CASSANDRA-11112
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11112
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Brandon Williams
>
> Currently there is no way to tell from a trace if a request is being sent by SR or not,
which can lead to confusion and make it hard to reason about why a query took a given path.



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

Mime
View raw message