Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 679AE200C5A for ; Tue, 18 Apr 2017 13:34:51 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 6634A160BAC; Tue, 18 Apr 2017 11:34:51 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id AEE37160B90 for ; Tue, 18 Apr 2017 13:34:50 +0200 (CEST) Received: (qmail 17646 invoked by uid 500); 18 Apr 2017 11:34:49 -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 17634 invoked by uid 99); 18 Apr 2017 11:34:49 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Apr 2017 11:34:49 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 81437CA726 for ; Tue, 18 Apr 2017 11:34:49 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 62HhKMjuc6pj for ; Tue, 18 Apr 2017 11:34:49 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 6009E5FB29 for ; Tue, 18 Apr 2017 11:34:43 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 66D69E0875 for ; Tue, 18 Apr 2017 11:34:42 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id DD0EC21B4F for ; Tue, 18 Apr 2017 11:34:41 +0000 (UTC) Date: Tue, 18 Apr 2017 11:34:41 +0000 (UTC) From: "Fuud (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CASSANDRA-13456) Needs better logging for timeout/failures MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 18 Apr 2017 11:34:51 -0000 Fuud created CASSANDRA-13456: -------------------------------- Summary: Needs better logging for timeout/failures Key: CASSANDRA-13456 URL: https://issues.apache.org/jira/browse/CASSANDRA-13456 Project: Cassandra Issue Type: Bug Reporter: Fuud When read was failed due to timeout, Cassandra reports in logs "Timeout; reveived 1 of 3 responses". Same information is passed to clients. But this information is not enoght to get list of slow nodes. Better to have detailed message in debug log: "Timeout; reveived 1 of 4 responses. Requested but not responded node: [, ], Failed nodes: []" I implemented such behavior by patching ReadCallback, AbstractWriteResponseHandler, DatacenterSyncWriteResponseHandler and WriteResponseHandler. It handles all cases except Paxos. But I want to implement solid solution that handle all cases in same way. But before I will start I want to know: are there any objections against such logging? -- This message was sent by Atlassian JIRA (v6.3.15#6346)