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 BBFEAD2DB for ; Thu, 1 Nov 2012 15:17:36 +0000 (UTC) Received: (qmail 27226 invoked by uid 500); 1 Nov 2012 15:17:34 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 27086 invoked by uid 500); 1 Nov 2012 15:17:33 -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 27053 invoked by uid 99); 1 Nov 2012 15:17:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2012 15:17:32 +0000 X-ASF-Spam-Status: No, hits=0.3 required=5.0 tests=FREEMAIL_REPLY,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of btoddb@gmail.com designates 209.85.214.172 as permitted sender) Received: from [209.85.214.172] (HELO mail-ob0-f172.google.com) (209.85.214.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2012 15:17:25 +0000 Received: by mail-ob0-f172.google.com with SMTP id v19so2861126obq.31 for ; Thu, 01 Nov 2012 08:17:04 -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:content-transfer-encoding; bh=NjzHPzSEtb4+G3aANYHPrPL+OetTlmifpTlbPN3q7r0=; b=z4oAKUD6Pp/KRX2mYqF6gzV1yp3626mgGmeIRxf4gR4qsoK8YWmSmLgNqsWLxDQCA2 Y4x7P2zYzgmmliu50GKGLUJX4nEMdCJ4XnumbagGDEHxq8RidJPAbVEXsy+bSSCSPceE 86LzfpWRNCmGZWARh/UxDsMzz6XZER1Z9nN28VwKAjaqP5HqK5LPHeufPHJg8EnLYQUB 4MfBp27X0WKGIUvd0+zbnYEcl/b7XjSm+CRHUVVslMkwaxYd8Qxim+5neEjIH2YO7Bsd NtJmpBGSBCpwAsWD1Fq9HaKpKjUKTcL387BZo3vmhLhATTNwK4B9FlyHsavLgKUJN8ow l3/w== MIME-Version: 1.0 Received: by 10.60.170.176 with SMTP id an16mr34296838oec.57.1351783024836; Thu, 01 Nov 2012 08:17:04 -0700 (PDT) Received: by 10.182.171.8 with HTTP; Thu, 1 Nov 2012 08:17:04 -0700 (PDT) In-Reply-To: References: <054A19B0E41FDD43A58D2CC1E8C3FF5B30725217@FISH-MBX-01.azaleos.net> <054A19B0E41FDD43A58D2CC1E8C3FF5B3072A0F3@FISH-MBX-01.azaleos.net> Date: Thu, 1 Nov 2012 08:17:04 -0700 Message-ID: Subject: Re: High bandwidth usage between datacenters for cluster From: "B. Todd Burruss" To: user@cassandra.apache.org Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org bryce, did you resolve this? i'm interested in the outcome. when you write does it help to use CL =3D LOCAL_QUORUM? On Mon, Oct 29, 2012 at 12:52 AM, aaron morton wr= ote: > Outbound messages for other DC's are grouped and a single instance is sen= t > to a single node in the remote DC. The remote node then forwards the mess= age > on to the other recipients in it's DC. All remote DC nodes will however > reply directly to the coordinator. > > Normally this isn=92t an issue for us, but at times we are writing > approximately 1MB a sec of data, and seeing a corresponding 3MB of traffi= c > across the WAN to all the Cassandra DR servers. > > Can you break the traffic down by port and direction ? > > Cheers > > > > ----------------- > Aaron Morton > Freelance Developer > @aaronmorton > http://www.thelastpickle.com > > On 28/10/2012, at 12:18 PM, Bryce Godfrey wro= te: > > Network topology with the topology file filled out is already the > configuration we are using. > > From: sankalp kohli [mailto:kohlisankalp@gmail.com] > Sent: Thursday, October 25, 2012 11:55 AM > To: user@cassandra.apache.org > Subject: Re: High bandwidth usage between datacenters for cluster > > Use placement_strategy =3D > 'org.apache.cassandra.locator.NetworkTopologyStrategy' and also fill the > topology.properties file. This will tell cassandra that you have two DCs. > You can verify that by looking at output of the ring command. > > If you DCs are setup properly, only one request will go over WAN. Though = the > responses from all nodes in other DC will go over WAN. > > On Thu, Oct 25, 2012 at 10:44 AM, Bryce Godfrey > wrote: > > We have a 5 node cluster, with a matching 5 nodes for DR in another data > center. With a replication factor of 3, does the node I send a write to= o > attempt to send it to the 3 servers in the DR also? Or does it send it t= o 1 > and let it replicate locally in the DR environment to save bandwidth acro= ss > the WAN? > Normally this isn=92t an issue for us, but at times we are writing > approximately 1MB a sec of data, and seeing a corresponding 3MB of traffi= c > across the WAN to all the Cassandra DR servers. > > If my assumptions are right, is this configurable somehow for writing to = one > node and letting it do local replication? We are on 1.1.5 > > Thanks > >