Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 374A610AD6 for ; Tue, 16 Apr 2013 21:08:44 +0000 (UTC) Received: (qmail 15355 invoked by uid 500); 16 Apr 2013 21:08:41 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 15316 invoked by uid 500); 16 Apr 2013 21:08:41 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 15308 invoked by uid 99); 16 Apr 2013 21:08:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Apr 2013 21:08:41 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [208.113.200.5] (HELO homiemail-a81.g.dreamhost.com) (208.113.200.5) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Apr 2013 21:08:34 +0000 Received: from homiemail-a81.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a81.g.dreamhost.com (Postfix) with ESMTP id B3049A8076 for ; Tue, 16 Apr 2013 14:08:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thelastpickle.com; h=from :content-type:message-id:mime-version:subject:date:references:to :in-reply-to; s=thelastpickle.com; bh=auHQICYURg2whGWyfHWr2XOQuE I=; b=VIaB0S6qAbaMf9whGYTQ6LQ8IfVuxGQpgoODVzceE0W0pWjLiTQGQDy5vG jiwpeeUHxQGbk8LYVLkjhtJGk5k197yaAUy3kwtcFfAUibrfr1HDwY4YdTzXrnBP Se5Hwx3DfbwTJs5WmpgYbzAAIYzmILiUD4USH0awNdvXqEMCw= Received: from [172.16.1.8] (unknown [203.86.207.101]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: aaron@thelastpickle.com) by homiemail-a81.g.dreamhost.com (Postfix) with ESMTPSA id 32D84A8075 for ; Tue, 16 Apr 2013 14:08:13 -0700 (PDT) From: aaron morton Content-Type: multipart/alternative; boundary="Apple-Mail=_17C72B33-1B80-49ED-8DCF-28A5589545E8" Message-Id: <2027FF56-EA9B-48B3-BDB7-82DF9857C00E@thelastpickle.com> Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: re-execution of failed queries with rpc_timeout Date: Wed, 17 Apr 2013 09:08:13 +1200 References: To: user@cassandra.apache.org In-Reply-To: X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_17C72B33-1B80-49ED-8DCF-28A5589545E8 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 If you are using Counters you need to do everything you can to avoid = timeouts. In the worse case we do not know where it has been applied. = The increment is applied on a lead and then replicated to the others, if = the coordinator is not the lead it may not know if the increments was = applied at all.=20 Start by reducing the size of the updates. Larger batches do not always = mean better performance.=20 > In all other cases, the rpc_timeout might be thrown from a remote = node (not the one I'm connected to), and hence some parts of the update = will be performed and others parts will not. TimedOutException is always thrown from the coordinator you are = connected to.=20 Cheers ----------------- Aaron Morton Freelance Cassandra Consultant New Zealand @aaronmorton http://www.thelastpickle.com On 15/04/2013, at 1:38 PM, Moty Kosharovsky wrote: > Sorry, not LOCAL QUORUM, I meant "ANY" quorum. >=20 >=20 > On Mon, Apr 15, 2013 at 4:12 AM, Moty Kosharovsky = wrote: > Hello, >=20 > I'm running a 12 node cluser with cassandra 1.1.5 and oracle jdk = 1.6.0_35. Our application constantly writes large updates with cql. Once = in a while, an rpc_time will occur. >=20 > Since a lot of the information is counters, its impossible for me to = understand if the updates complete partially on rpc_timeout, or = cassandra somehow rolls back the change completely, and hence I can't = tell if I should re-execute the query on rpc_timeout (with double = processing being a bigger concern than missing updates). >=20 > I am thinking, but unsure of this, that if I'll switch to = LOCAL_QUORUM, rpc_timeout will always mean that the update was not = processes as a whole. In all other cases, the rpc_timeout might be = thrown from a remote node (not the one I'm connected to), and hence some = parts of the update will be performed and others parts will not. >=20 > Anyone solved this issue before? >=20 > Kind Regards, > Kosha >=20 --Apple-Mail=_17C72B33-1B80-49ED-8DCF-28A5589545E8 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 If = you are using Counters you need to do everything you can to avoid = timeouts. In the worse case we do not know where it has been applied. = The increment is applied on a lead and then replicated to the others, if = the coordinator is not  the lead it may not know if the increments = was applied at all. 

Start by reducing the size = of the updates. Larger batches do not always mean better = performance. 

 In all other cases, the rpc_timeout might = be thrown from a remote node (not the one I'm connected to), and hence = some parts of the update will be performed and others parts will = not.
TimedOutException is = always thrown from the coordinator you are connected = to. 

Cheers

http://www.thelastpickle.com

On 15/04/2013, at 1:38 PM, Moty Kosharovsky <motykosh@gmail.com> = wrote:

Sorry, not LOCAL QUORUM, I meant "ANY" = quorum.


On Mon, Apr 15, 2013 at 4:12 AM, Moty Kosharovsky = <motykosh@gmail.com> wrote:
Hello,

I'm running a 12 node = cluser with cassandra 1.1.5 and oracle jdk 1.6.0_35. Our application = constantly writes large updates with cql. Once in a while, an rpc_time = will occur.

Since a lot of the information is counters, its = impossible for me to understand if the updates complete partially on = rpc_timeout, or cassandra somehow rolls back the change completely, and = hence I can't tell if I should re-execute the query on rpc_timeout (with = double processing being a bigger concern than missing updates).

I am thinking, but unsure of this, that if I'll = switch to LOCAL_QUORUM, rpc_timeout will always mean that the update was = not processes as a whole. In all other cases, the rpc_timeout might be = thrown from a remote node (not the one I'm connected to), and hence some = parts of the update will be performed and others parts will not.

Anyone solved this issue = before?

Kind = Regards,
Kosha


= --Apple-Mail=_17C72B33-1B80-49ED-8DCF-28A5589545E8--