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 62DA510A34 for ; Wed, 26 Jun 2013 01:59:12 +0000 (UTC) Received: (qmail 13715 invoked by uid 500); 26 Jun 2013 01:59:10 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 13695 invoked by uid 500); 26 Jun 2013 01:59:09 -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 13685 invoked by uid 99); 26 Jun 2013 01:59:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Jun 2013 01:59:09 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kohlisankalp@gmail.com designates 209.85.216.180 as permitted sender) Received: from [209.85.216.180] (HELO mail-qc0-f180.google.com) (209.85.216.180) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Jun 2013 01:59:04 +0000 Received: by mail-qc0-f180.google.com with SMTP id a1so7783799qcx.39 for ; Tue, 25 Jun 2013 18:58:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=UVaxLHT9Fp+eJlLjeTxxB747WKef7YyH4hxOt0SJDOQ=; b=WiUb26W5p/T/esI3LBTeMTWHeJasdgijyf+5zInP+LNbhX9qJljucHyg+PS4+S8ShA lb0dzuj4JqUIPOJC2pyouH/y9c3fbsyYwh+04mpItjph+0kRnZ8lnxx8gd6MJuE3U/yx kPrmnOTJ7+J4xb9GbNdsm8ii0xVrYNBbn5rX1vv8KsoGGBV0bOc0sO+YJS2BFnGvwXtu zxxNuoRfKi6mCajVIYOnde4ID0A6wn8vPPyAt/ManQbzWa8wuG/3g3BPGK4l0+3uIV+p 7fiiKIIIYOwgIi5t2FamprYYTcwOuB4LlwFSyaePXIacOXfmfJYRyThrCyy4qmYpCOMZ wwiA== X-Received: by 10.229.163.84 with SMTP id z20mr429773qcx.75.1372211923707; Tue, 25 Jun 2013 18:58:43 -0700 (PDT) MIME-Version: 1.0 Received: by 10.49.104.199 with HTTP; Tue, 25 Jun 2013 18:58:03 -0700 (PDT) In-Reply-To: References: From: sankalp kohli Date: Tue, 25 Jun 2013 21:58:03 -0400 Message-ID: Subject: Re: what happen if coordinator node fails during write To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=14dae9c093de44ee0c04e004fc0f X-Virus-Checked: Checked by ClamAV on apache.org --14dae9c093de44ee0c04e004fc0f Content-Type: text/plain; charset=ISO-8859-1 Read this http://www.datastax.com/dev/blog/atomic-batches-in-cassandra-1-2 On Tue, Jun 25, 2013 at 8:45 PM, Andrey Ilinykh wrote: > It depends on cassandra version. As far as I know in 1.2 coordinator logs > request before it updates replicas. If it fails it will replay log on > startup. > In 1.1 you may have inconsistant state, because only part of your request > is propagated to replicas. > > Thank you, > Andrey > > > On Tue, Jun 25, 2013 at 5:11 PM, Jiaan Zeng wrote: > >> Hi there, >> >> I am writing data to Cassandra by thrift client (not hector) and >> wonder what happen if the coordinator node fails. The same question >> applies for bulk loader which uses gossip protocol instead of thrift >> protocol. In my understanding, the HintedHandoff only takes care of >> the replica node fails. >> >> Thanks. >> >> -- >> Regards, >> Jiaan >> > > --14dae9c093de44ee0c04e004fc0f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Tue, Jun 25, 2013 at 8:45 PM, Andrey Ilinykh = <ailinykh@gmail.com> wrote:
It depends on cassandra version. As far as I know in 1.2 c= oordinator logs request before it updates replicas. If it fails it will rep= lay log on startup.
In 1.1 you may have inconsistant state, because onl= y part of your request is=A0propagated=A0to replicas.

Thank you,
=A0 Andrey


On Tue, Jun 25, 2013 at 5:11 PM, Jiaan Zeng <jiaan@blo= omreach.com> wrote:
Hi there,

I am writing data to Cassandra by thrift client (not hector) and
wonder what happen if the coordinator node fails. The same question
applies for bulk loader which uses gossip protocol instead of thrift
protocol. In my understanding, the HintedHandoff only takes care of
the replica node fails.

Thanks.

--
Regards,
Jiaan


--14dae9c093de44ee0c04e004fc0f--