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 6D404C99E for ; Thu, 11 Jul 2013 09:53:53 +0000 (UTC) Received: (qmail 55180 invoked by uid 500); 11 Jul 2013 09:53:50 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 55155 invoked by uid 500); 11 Jul 2013 09:53:49 -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 55128 invoked by uid 99); 11 Jul 2013 09:53:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Jul 2013 09:53:48 +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 chris.wirt@struq.com designates 209.85.215.181 as permitted sender) Received: from [209.85.215.181] (HELO mail-ea0-f181.google.com) (209.85.215.181) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Jul 2013 09:53:40 +0000 Received: by mail-ea0-f181.google.com with SMTP id a15so5619066eae.12 for ; Thu, 11 Jul 2013 02:53:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:to:subject:date:message-id:mime-version:content-type:x-mailer :thread-index:content-language:x-gm-message-state; bh=NovKXr5+b+EXVLGDXCPYyErLM+rqCA7MKaq3pfZR9pw=; b=gcaCguIocsC3sqIcMDKiuAMJ9+150xipG2pRcoC2Rc4Pg/CRRJTHBB4bbYF0eGqUtu IIVXQuU/TThUkBp4R9lNv+jNmrBvKWFVZFYBhmD9hy01cnIvtiiZ+3i9zAEdA5FkoJQ1 EX/BchyGov2Aytu3bHX9535PTmwc3cehZ0WetTriCYD3184Grt+ql5uYfg1XaYEQrEKd sWrPgkjZUhcX/4Iyy3mcQtsSW1TSHmZPTgjzynvVIqTn03aH0YP6z2AelIiumJdX/zIT epRwvk93l/J0npUkMU/oOdf9jQL6EKZT3+pRSKmeRjEDy3YPLn5AJAsakc/7oMXNpuRS CH7g== X-Received: by 10.15.64.202 with SMTP id o50mr40953131eex.44.1373536400301; Thu, 11 Jul 2013 02:53:20 -0700 (PDT) Received: from StevePereiraPC (host81-133-200-21.in-addr.btopenworld.com. [81.133.200.21]) by mx.google.com with ESMTPSA id b3sm67646240eev.10.2013.07.11.02.53.19 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 11 Jul 2013 02:53:19 -0700 (PDT) From: "Christopher Wirt" To: Subject: listen_address and rpc_address address on different interface Date: Thu, 11 Jul 2013 10:53:17 +0100 Message-ID: <009d01ce7e1c$7909ea00$6b1dbe00$@struq.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_009E_01CE7E24.DACFFFB0" X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac5+FzdS3RCXcZ/3Qk2Vis/JaWcOgg== Content-Language: en-gb X-Gm-Message-State: ALoCoQkVDgh/h+HUDmwN9gOorsT0o8qCMXm3S6S86qLASvmPv9xrQseXRXIVIff9paOHwOx2+VJu X-Virus-Checked: Checked by ClamAV on apache.org This is a multipart message in MIME format. ------=_NextPart_000_009E_01CE7E24.DACFFFB0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello, I was wondering if anyone has measured the performance improvements to having the listen address and client address bound to different interface? We a have 2gbit connection serving both at the moment and this doesn't come close to being saturated. But being very keen on fast reads at the 99th percentile we're interested in even the smallest improvements. Next question - Has anyone ever moved an existing node to have the listen address and client access address bound to different addresses? Our Problem Currently our only address is a DNS entry which we would like to keep bound to the client access. If we were to take down a node and change the listen address then re-join the ring, the other nodes will mark the node as dead when we take it down and assume we have a new node when we bring it back on a different address. Lots of wasted rebalancing and compaction will start. We use Cassandra 1.2.4 w/vnodes. Not sure there will be anyway around this. So back to question one, am I wasting my time? Thanks, Chris ------=_NextPart_000_009E_01CE7E24.DACFFFB0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello,

 

I was = wondering if anyone has measured the performance improvements to having = the listen address and client address bound to different = interface?

 

We a have 2gbit connection serving both at the moment = and this doesn’t come close to being saturated. But being very = keen on fast reads at the 99th percentile we’re = interested in even the smallest improvements.

 

Next = question - Has anyone ever moved an existing node to have the listen = address and client access address bound to different = addresses?

 

Our Problem 

Currently our only address is a DNS entry which we = would like to keep bound to the client access.

If we were to take down a node and change the listen = address then re-join the ring, the other nodes will mark the node as = dead when we take it down and assume we have a new node when we bring it = back on a different address.

Lots of = wasted rebalancing and compaction will start.

We use Cassandra 1.2.4 w/vnodes.

Not sure there will be anyway around = this.

So back to question one, am I = wasting my time?

 

=

Thanks,

Chris

 

 

 

------=_NextPart_000_009E_01CE7E24.DACFFFB0--