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 489D3C5CF for ; Wed, 10 Dec 2014 10:20:13 +0000 (UTC) Received: (qmail 27231 invoked by uid 500); 10 Dec 2014 10:20:13 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 27197 invoked by uid 500); 10 Dec 2014 10:20:12 -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 27186 invoked by uid 99); 10 Dec 2014 10:20:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Dec 2014 10:20:12 +0000 Date: Wed, 10 Dec 2014 10:20:12 +0000 (UTC) From: "Sam Tunnicliffe (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-7947) Change error message when RR times out 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-7947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-7947: --------------------------------------- Attachment: 7947.txt Attaching a simple patch which correctly sets the CL on the thrown exception. Looks like this is only an issue when read requests following a digest mismatch time out, if we timeout waiting on acks for the subsequent mutations, the correct CL is communicated. > Change error message when RR times out > -------------------------------------- > > Key: CASSANDRA-7947 > URL: https://issues.apache.org/jira/browse/CASSANDRA-7947 > Project: Cassandra > Issue Type: Improvement > Components: Core > Reporter: Brandon Williams > Assignee: Sam Tunnicliffe > Priority: Minor > Fix For: 2.0.12 > > Attachments: 7947.txt > > > When a quorum request detects a checksum mismatch, it then reads the data to repair the mismatch by issuing a request at CL.ALL to the same endpoints (SP.fetchRows) If this request in turn times out, this delivers a TOE to the client with a misleading message that mentions CL.ALL, possibly causing them to think the request has gone cross-DC when it has not, it was just slow due to timing out. -- This message was sent by Atlassian JIRA (v6.3.4#6332)