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 891EC17F8D for ; Tue, 28 Oct 2014 10:38:50 +0000 (UTC) Received: (qmail 78329 invoked by uid 500); 28 Oct 2014 10:38:47 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 78290 invoked by uid 500); 28 Oct 2014 10:38:47 -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 78280 invoked by uid 99); 28 Oct 2014 10:38:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Oct 2014 10:38:47 +0000 X-ASF-Spam-Status: No, hits=-2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_HI,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of basit.b.syed@nsn.com designates 93.183.12.32 as permitted sender) Received: from [93.183.12.32] (HELO demumfd001.nsn-inter.net) (93.183.12.32) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Oct 2014 10:38:16 +0000 Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.14.3/8.14.3) with ESMTP id s9SAc4mw002818 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 28 Oct 2014 10:38:04 GMT Received: from DEMUHTC003.nsn-intra.net ([10.159.42.34]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id s9SAc4Id028755 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Tue, 28 Oct 2014 11:38:04 +0100 Received: from DEMUHTC009.nsn-intra.net (10.159.42.40) by DEMUHTC003.nsn-intra.net (10.159.42.34) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 28 Oct 2014 11:38:03 +0100 Received: from DEMUMBX011.nsn-intra.net ([169.254.11.150]) by DEMUHTC009.nsn-intra.net ([10.159.42.40]) with mapi id 14.03.0195.001; Tue, 28 Oct 2014 11:38:03 +0100 From: "Syed, Basit B. (NSN - FI/Espoo)" To: "user@cassandra.apache.org" Subject: Load balancing in C* Cluster Thread-Topic: Load balancing in C* Cluster Thread-Index: Ac/ymz5Or46GHEolSWOujWbPR+qftg== Date: Tue, 28 Oct 2014 10:38:00 +0000 Message-ID: <7D0D3D25E7C52E439B5BC417DC0C7A831670F551@DEMUMBX011.nsn-intra.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.159.42.117] Content-Type: multipart/alternative; boundary="_000_7D0D3D25E7C52E439B5BC417DC0C7A831670F551DEMUMBX011nsnin_" MIME-Version: 1.0 X-purgate-type: clean X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de X-purgate: clean X-purgate: This mail is considered clean (visit http://www.eleven.de for further information) X-purgate-size: 2580 X-purgate-ID: 151667::1414492684-0000437E-99213A87/0/0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_7D0D3D25E7C52E439B5BC417DC0C7A831670F551DEMUMBX011nsnin_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, I am learning C* and its usage these days. I have a very simple, possibly n= aive question about load balancing. I know that C* can automatically balance the load itself by using tokens. B= ut what about connecting my cluster to a system. For exp, if we have a clie= nt or a set of clients (e.g. 12 client machines) accessing a 3-node C* clus= ter. All three nodes are independent and talk with each other through gossi= p. This means that we have three IP addresses to connect to a cluster. What should be the best strategy for clients to access these IP addresses? = Should we connect four clients each to only one node? OR all 12 clients sho= uld see and connect all three nodes? Which strategy is better? Is there any= resources available on web for this kind of issue? Regards, Basit --_000_7D0D3D25E7C52E439B5BC417DC0C7A831670F551DEMUMBX011nsnin_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hi,
I am learning C* and its usage these days. I have a very simple, possi= bly naive question about load balancing.
 
I know that C* can automatically balance the load itself by using toke= ns. But what about connecting my cluster to a system. For exp, if we have a= client or a set of clients (e.g. 12 client machines) accessing a 3-node C*= cluster. All three nodes are independent and talk with each other through gossip. This means that we have three IP a= ddresses to connect to a cluster.
 
What should be the best strategy for clients to access these IP addres= ses? Should we connect four clients each to only one node? OR all 12 client= s should see and connect all three nodes? Which strategy is better? Is ther= e any resources available on web for this kind of issue?
 
Regards,
Basit
 
--_000_7D0D3D25E7C52E439B5BC417DC0C7A831670F551DEMUMBX011nsnin_--