Return-Path: Delivered-To: apmail-incubator-cassandra-user-archive@minotaur.apache.org Received: (qmail 99214 invoked from network); 3 Mar 2010 17:35:09 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 3 Mar 2010 17:35:09 -0000 Received: (qmail 68475 invoked by uid 500); 3 Mar 2010 17:35:01 -0000 Delivered-To: apmail-incubator-cassandra-user-archive@incubator.apache.org Received: (qmail 68451 invoked by uid 500); 3 Mar 2010 17:35:01 -0000 Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cassandra-user@incubator.apache.org Delivered-To: mailing list cassandra-user@incubator.apache.org Received: (qmail 68443 invoked by uid 99); 3 Mar 2010 17:35:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Mar 2010 17:35:01 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of christopher.brind@googlemail.com designates 209.85.219.210 as permitted sender) Received: from [209.85.219.210] (HELO mail-ew0-f210.google.com) (209.85.219.210) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Mar 2010 17:34:51 +0000 Received: by ewy2 with SMTP id 2so1088904ewy.20 for ; Wed, 03 Mar 2010 09:34:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=MkVZNF5IuHcwmA78SdU7OJjBU+MYIkwVse44wdlMtvk=; b=YvFTWS63EOyxC8qVTeu0icHulioxtafRFYnB9rbYqWqPf9WODyTiaJXUngr4lWxR2X XaM2k+M5dRFp05zpCxtZZQ5AK7tg7VYpOOyOjbfoTIc+Y8a18pfmsleLCqCD9Mi0QbcM UH6jGhN9AUtBG2sfvQLO3vd7rB4YRMTSIQ3dc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=vYDSF4rv1Eyv8PcEcA42c2tBVcAaA3fgT+ldzVJqr3LICRJ6DfDZVjvYcS5yOFqPac w/XElW5/UmYXMnwQAw1wyg6G5JKYwKG/iMsdN+uDhdnXGuLKzag+O0p5CBURzl6nVssM z5oS6OJ4a1a1KhlDiGBtElcFWCx5Xs3Pdku8s= MIME-Version: 1.0 Sender: christopher.brind@googlemail.com Received: by 10.216.88.10 with SMTP id z10mr4203561wee.108.1267637669920; Wed, 03 Mar 2010 09:34:29 -0800 (PST) In-Reply-To: <1267637256.17434.53.camel@erebus.lan> References: <87hbozq574.fsf@lifelogs.com> <1c6fcff1003030557v527c2dcbn78e1ea9f93adc328@mail.gmail.com> <87k4ttqy8k.fsf@lifelogs.com> <1c6fcff1003030641g4737155fl4cb9b901bd9ebf13@mail.gmail.com> <87zl2pphvd.fsf@lifelogs.com> <1c6fcff1003030732i5b17be81g38629aaaaa3eecb@mail.gmail.com> <87fx4hpezm.fsf@lifelogs.com> <1267634599.17434.30.camel@erebus.lan> <36fe576b1003030849v5281365ag9f3e644152337523@mail.gmail.com> <1267637256.17434.53.camel@erebus.lan> Date: Wed, 3 Mar 2010 17:34:29 +0000 X-Google-Sender-Auth: 5b25644ca0687e23 Message-ID: <36fe576b1003030934k1e5866adnbec2855a7ff1cec5@mail.gmail.com> Subject: Re: finding Cassandra servers From: Christopher Brind To: cassandra-user@incubator.apache.org Content-Type: multipart/alternative; boundary=0016e6d7854604ffaa0480e8e5ea X-Virus-Checked: Checked by ClamAV on apache.org --0016e6d7854604ffaa0480e8e5ea Content-Type: text/plain; charset=UTF-8 Great, thanks Eric On 3 Mar 2010 17:27, "Eric Evans" wrote: On Wed, 2010-03-03 at 16:49 +0000, Christopher Brind wrote: > So is the current general practice to ... There are so many ways you could tackle this but... If you're talking about provisioning/startup of new nodes, just use the IPs of 2-4 nodes in the seeds section of configs. If you're talking about clients, then round-robin DNS is one option. Load-balancers are another. Either could be used with a subset of higher-capacity/higher-availability nodes, or for the entire cluster. > If so, what happens if that node is down? Is the entire cluster > effectively broken at that poi... You don't use just one node, see above. > Or do clients simply maintain a list of nodes a just connect to the > first available in the list... It's possible to obtain a list of nodes over Thrift. So, yet another option would be to use a short-list of well-known nodes (discovered via round-robin DNS for example), to obtain a current node list and distribute among them. -- Eric Evans eevans@rackspace.com --0016e6d7854604ffaa0480e8e5ea Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Great,=C2=A0 thanks Eric

On 3 Mar 2010 17:27, "Eric Evans" &l= t;eevans@rackspace.com> wrot= e:

On Wed, 2010-03-03 at 16:49 +0000, Chr= istopher Brind wrote:
> So is the current general practice to ...

There are so many = ways you could tackle this but...

If you're talking about provisioning/startup of new nodes, just use the=
IPs of 2-4 nodes in the seeds section of configs.

If you're talking about clients, then round-robin DNS is one option. Load-balancers are another. Either could be used with a subset of
higher-capacity/higher-availability nodes, or for the entire cluster.


> If so, what happens if that node is dow= n? Is the entire cluster
> effectively broken at that poi...<= /p>You don't use just one node, see above.


> Or do clients simply maintain a list of= nodes a just connect to the
> first available in the list...<= /p>It's possible to obtain a list of nodes over Thrift. So, yet another=
option would be to use a short-list of well-known nodes (discovered via
round-robin DNS for example), to obtain a current node list and
distribute among them.

--

Eric Evans
eevans@rackspace.com

--0016e6d7854604ffaa0480e8e5ea--