Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EA75317F29 for ; Wed, 22 Apr 2015 19:00:59 +0000 (UTC) Received: (qmail 19179 invoked by uid 500); 22 Apr 2015 19:00:59 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 19119 invoked by uid 500); 22 Apr 2015 19:00:59 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 18887 invoked by uid 99); 22 Apr 2015 19:00:59 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Apr 2015 19:00:59 +0000 Date: Wed, 22 Apr 2015 19:00:59 +0000 (UTC) From: "Vishy Kasar (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (CASSANDRA-9226) Log streamid at the trace level on sending request and receiving response MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-9226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishy Kasar resolved CASSANDRA-9226. ------------------------------------ Resolution: Invalid > Log streamid at the trace level on sending request and receiving response > ------------------------------------------------------------------------- > > Key: CASSANDRA-9226 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9226 > Project: Cassandra > Issue Type: Improvement > Components: Core > Reporter: Vishy Kasar > > Multiple requests are sent on the same connection and responses arrive in any order. It is hard to track single request/response pair even when the trace logs are turned on today because the trace logs only provide information up to connection as shown below. It will be super useful to also provide the streamid in the trace logs. > 2015/04/17 14:02:43.334 TRACE [New I/O worker #447] com.datastax.driver.core.Connection - Connection[host1.domain.com/10.0.1.1:9042-1, inFlight=1, closed=false] request sent successfully > 2015/04/17 14:02:43.337 TRACE [New I/O worker #447] com.datastax.driver.core.Connection - Connection[host1.domain.com/10.0.1.1:9042-1, inFlight=1, closed=false] received: ROWS [column1 (timeuuid)][value (blob)][writetime(value) (bigint)] > streamid will be useful at-least in the 2 logs above. But if you know of other cases where it will be useful, please add it there as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)