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 ADFA9DD47 for ; Tue, 26 Jun 2012 15:17:12 +0000 (UTC) Received: (qmail 55060 invoked by uid 500); 26 Jun 2012 15:17:10 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 55034 invoked by uid 500); 26 Jun 2012 15:17:10 -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 55026 invoked by uid 99); 26 Jun 2012 15:17:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Jun 2012 15:17:10 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_REPLY,FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of karthik.nar@gmail.com designates 209.85.213.172 as permitted sender) Received: from [209.85.213.172] (HELO mail-yx0-f172.google.com) (209.85.213.172) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Jun 2012 15:17:02 +0000 Received: by yenq13 with SMTP id q13so11696yen.31 for ; Tue, 26 Jun 2012 08:16:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=HwV9DWJQ48BtuiyIVdIxmi504L/uhNpAbt6MdU/wEBg=; b=WRpDwiTgGWh3seTm8zgNcdQM2aRFe4crguThgoEPs48ecR6BvkE9kyajzSy9jUKM0e 17L0XqTbSQeAIZZQGAC6fi1gdXgcpooDqw6wqnHlx+xlM5bKDYuZ2mMkV5TFbhspP7vI eHkTn9I6smgvXLrpOM45H43KQYgKmjFAjnNso5qXS/P1npPL/GaCByYGv6ryRylXlc49 RSjysNWtSfbyWmwm5iBntDrAIMjjSPYpDEd53I1JnvfBdne3wtt+N2T5lJWd7yNhus/e vPpxm9Gz7/bqmJZEKzqUp1uCQrY2oAPAQ6yINXIm1sy1xYCyGj47jRjbdWK/lESoX9C8 MR+g== MIME-Version: 1.0 Received: by 10.50.207.104 with SMTP id lv8mr11515184igc.41.1340723801339; Tue, 26 Jun 2012 08:16:41 -0700 (PDT) Received: by 10.231.153.83 with HTTP; Tue, 26 Jun 2012 08:16:41 -0700 (PDT) In-Reply-To: References: Date: Tue, 26 Jun 2012 08:16:41 -0700 Message-ID: Subject: Re: Multi datacenter, WAN hiccups and replication From: Karthik N To: "user@cassandra.apache.org" Content-Type: multipart/alternative; boundary=14dae9340fbdebb83f04c36195ea --14dae9340fbdebb83f04c36195ea Content-Type: text/plain; charset=ISO-8859-1 Since Cassandra optimizes and sends only one copy over the WAN, can I opt in only for HH for WAN replication and avoid HH for the local quorum? (since I know I have more copies) On Tuesday, June 26, 2012, Mohit Anchlia wrote: > > On Tue, Jun 26, 2012 at 7:52 AM, Karthik N > > wrote: > >> My Cassandra ring spans two DCs. I use local quorum with replication >> factor=3. I do a write in DC1 with local quorum. Data gets written to >> multiple nodes in DC1. For the same write to propagate to DC2 only one >> copy is sent from the coordinator node in DC1 to a coordinator node in >> DC2 for optimizing traffic over the WAN (from what I have read in the >> Cassandra documentation) >> >> Will a Wan hiccup result in a Hinted Handoff (HH) being created in >> DC1's coordinator for DC2 to be delivered when the Wan link is up >> again? >> > > I have seen hinted handoff messages in the log files when the remote DC is > unreachable. But this mechanism is only used for a the time defined in > cassandra.yaml file. -- Thanks, Karthik --14dae9340fbdebb83f04c36195ea Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Since Cassandra optimizes and sends only one copy over the WAN, can I opt i= n only for HH for WAN replication and avoid HH for the local quorum? (since= I know I have more copies)=A0

On Tuesday, June 26= , 2012, Mohit Anchlia wrote:

On Tue, Jun 26, 2012 at 7:52 AM, Karthik N <karthik.nar@gmail.com> wrote:
My Cassandra ring spans two DCs. I us= e local quorum with replication
factor=3D3. I do a write in DC1 with loc= al quorum. Data gets written to
multiple nodes in DC1. For the same write to propagate to DC2 only one
c= opy is sent from the coordinator node in DC1 to a coordinator node in
DC= 2 for optimizing traffic over the WAN (from what I have read in the
Cassandra documentation)

Will a Wan hiccup result in a Hinted Handof= f (HH) being created in
DC1's coordinator for DC2 to be delivered wh= en the Wan link is up
again?

I have seen hinte= d handoff messages in the log files when the remote DC is unreachable. But = this mechanism is only used for a the time defined in cassandra.yaml file.


--
Thanks, Karthik
--14dae9340fbdebb83f04c36195ea--