Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 29 Jul 2014 21:06:39 +0000 (UTC)
From: "Brandon Williams (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12729955.1406323562000.69406.1406667999038@arcas>
In-Reply-To: <JIRA.12729955.1406323562000@arcas>
References: <JIRA.12729955.1406323562000@arcas>
Subject: [jira] [Assigned] (CASSANDRA-7629) tracing no longer logs when the
 request completed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Brandon Williams reassigned CASSANDRA-7629:
-------------------------------------------

    Assignee: Tyler Hobbs

> 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)