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 24BCB1021D for ; Wed, 12 Feb 2014 20:18:08 +0000 (UTC) Received: (qmail 56915 invoked by uid 500); 12 Feb 2014 20:18:05 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 56852 invoked by uid 500); 12 Feb 2014 20:18:04 -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 56844 invoked by uid 99); 12 Feb 2014 20:18:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Feb 2014 20:18:04 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rbradberry@gmail.com designates 209.85.216.174 as permitted sender) Received: from [209.85.216.174] (HELO mail-qc0-f174.google.com) (209.85.216.174) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Feb 2014 20:18:00 +0000 Received: by mail-qc0-f174.google.com with SMTP id x13so16010382qcv.19 for ; Wed, 12 Feb 2014 12:17:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :content-type; bh=L57AipjFbHiEYJIjTgtCPpSe2yucDIuXhMImx+P7HIA=; b=SxZTzers1BcRGFM2PXgjzEPQU0eZixBfz7Xy4sVEyrsoQ85+Apu0oOxNCCIDhxGQyJ ZtBksxxla3SR9z94c9yrNH0pTjPVA4cUrS2Ar1uAfJV3eLCy7kQAptdzIz7YcRgd7QPe EwJ+x+6Dc6ta8nBaB1GSh3mihRewAYcnk48cwxq1vpvAsMfxDrH+gizYOdPRmkJERoM8 ZmR/STZQRMOLpeZdvng7gNTju/7pUiJBOMYaiUoK6IhiLiPQLLxFtKKLZ7E7LH6nut/g VOLO5TNMA+r6K0oBeHSXHiaqjyLsXQQdO/RtD1maAMRI3iCjkotwpwb0tj6Pucz3BXAs sXTg== X-Received: by 10.140.23.209 with SMTP id 75mr67035754qgp.89.1392236259326; Wed, 12 Feb 2014 12:17:39 -0800 (PST) Received: from Russells-iMac.local (rrcs-24-136-119-106.nyc.biz.rr.com. [24.136.119.106]) by mx.google.com with ESMTPSA id a5sm66023541qae.2.2014.02.12.12.17.37 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 12 Feb 2014 12:17:38 -0800 (PST) Date: Wed, 12 Feb 2014 15:17:36 -0500 From: Russell Bradberry To: William Oberman , user@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: Re: in AWS is it worth trying to talk to a server in the same zone as your client? X-Mailer: Airmail (223) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="52fbd6e0_66334873_bbd1" X-Virus-Checked: Checked by ClamAV on apache.org --52fbd6e0_66334873_bbd1 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Not when using private IP addresses. =C2=A0That pricing ONLY applies if y= ou are using the public interface or EIP/ENI. =C2=A0If you use the privat= e IP addresses there is no cost associated. On =46ebruary 12, 2014 at 3:13:58 PM, William Oberman (oberman=40civicsci= ence.com) wrote: Same region, cross zone transfer is=C2=A0=240.01 / GB (see=C2=A0http://aw= s.amazon.com/ec2/pricing/, Data Transfer section). On Wed, =46eb 12, 2014 at 3:04 PM, Russell Bradberry wrote: Cross zone data transfer does not cost any extra money.=C2=A0 LOCAL=5FQUORUM =3D QUORUM if all 6 servers are located in the same logica= l datacenter. =C2=A0 Ensure your clients are connecting to either the local IP or the AWS host= name that is a CNAME to the local ip from within AWS. =C2=A0If you connec= t to the public IP you will get charged for outbound data transfer. On =46ebruary 12, 2014 at 2:58:07 PM, Yogi Nerella (ynerella999=40gmail.c= om) wrote: Also, may be you need to check the read consistency to local=5Fquorum, ot= herwise the servers still try to read the data from all other data center= s. I can understand the latency, but I cant understand how it would save mon= ey=3F =C2=A0 The amount of data transferred from the AWS server to the cl= ient should be same no matter where the client is connected=3F =C2=A0=C2=A0=C2=A0 On Wed, =46eb 12, 2014 at 10:33 AM, Andrey Ilinykh = wrote: yes, sure. Taking data from the same zone will reduce latency and save yo= u some money. On Wed, =46eb 12, 2014 at 10:13 AM, Brian Tarbox wrote: We're running a C* cluster with 6 servers spread across the four us-east1= zones. We also spread our clients (hundreds of them) across the four zones. Currently we give our clients a connection string listing all six servers= and let C* do its thing. This is all working just fine...and we're paying a fair bit in AWS transf= er costs. =C2=A0There is a suspicion that this transfer cost is driven by= us passing data around between our C* servers and clients. Would there be any value to trying to get a client to talk to one of the = C* servers in its own zone=3F I understand (at least partially=21) about coordinator nodes and replicat= ion and know that no matter which server is the coordinator for an operat= ion replication may cause bits to get transferred to/from servers in othe= r zones. =C2=A0Having said that...is there a chance that trying to encour= age a client to initially contact a server in its own zone would help=3F Thank you, Brian Tarbox --52fbd6e0_66334873_bbd1 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline