From cassandra-user-return-2906-apmail-incubator-cassandra-user-archive=incubator.apache.org@incubator.apache.org Wed Mar 03 16:50:14 2010 Return-Path: Delivered-To: apmail-incubator-cassandra-user-archive@minotaur.apache.org Received: (qmail 84920 invoked from network); 3 Mar 2010 16:50:14 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 3 Mar 2010 16:50:14 -0000 Received: (qmail 56163 invoked by uid 500); 3 Mar 2010 16:50:06 -0000 Delivered-To: apmail-incubator-cassandra-user-archive@incubator.apache.org Received: (qmail 56145 invoked by uid 500); 3 Mar 2010 16:50:06 -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 56137 invoked by uid 99); 3 Mar 2010 16:50:06 -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 16:50:06 +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 74.125.82.47 as permitted sender) Received: from [74.125.82.47] (HELO mail-ww0-f47.google.com) (74.125.82.47) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Mar 2010 16:49:56 +0000 Received: by wwb31 with SMTP id 31so142026wwb.6 for ; Wed, 03 Mar 2010 08:49:35 -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=oRyajz0/kgGPPs0tslhlTq3gKI7fEiMcpAWykW3J3fA=; b=WjDd8xXxNJXLIWYXmz42Pdnteh0YG2y/yhi37tTvQ/wblmABsgXF2vMp43uVEfsvM/ /p9LE/UEZWQ+bcSg/n+UiXDN++tioE90P5+B8yXpVrB2ic765yZGRg/6Hvi12eRcQyuh Olqeccsyec5TJ72hJW9MC8U/wKKuvRh5VjsLg= 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=d2mxYn33/OfHOuytH58rvUgF+XUaH+0R453A+KPpZK5awK+IVr2nyI72BFJNBXQ8WN FRnbhn6qxpFmW6G/5S5BUmilJ2Ld+J3xMTAgZcDxF/Of033wWYadj91uPewkNE+rv9fe lS3t/KbSwe5JfETpAZJ5bSJC9CagtJ2C9dxec= MIME-Version: 1.0 Sender: christopher.brind@googlemail.com Received: by 10.216.86.82 with SMTP id v60mr161261wee.180.1267634974519; Wed, 03 Mar 2010 08:49:34 -0800 (PST) In-Reply-To: <1267634599.17434.30.camel@erebus.lan> References: <87hbozq574.fsf@lifelogs.com> <87eik1lf8b.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> Date: Wed, 3 Mar 2010 16:49:34 +0000 X-Google-Sender-Auth: 533101f0f84acd6e Message-ID: <36fe576b1003030849v5281365ag9f3e644152337523@mail.gmail.com> Subject: Re: finding Cassandra servers From: Christopher Brind To: cassandra-user@incubator.apache.org Content-Type: multipart/alternative; boundary=0016e6d77e595d6dff0480e844a5 X-Virus-Checked: Checked by ClamAV on apache.org --0016e6d77e595d6dff0480e844a5 Content-Type: text/plain; charset=UTF-8 So is the current general practice to connect to a known node, e.g. by ip address? If so, what happens if that node is down? Is the entire cluster effectively broken at that point? Or do clients simply maintain a list of nodes a just connect to the first available in the list? Thanks in advance. Cheers Chris On 3 Mar 2010 16:43, "Eric Evans" wrote: On Wed, 2010-03-03 at 10:05 -0600, Ted Zlatanov wrote: > I can do a patch+ticket for this in the cor... I don't think voting is going to help. Voting doesn't do anything to develop consensus and it seems pretty clear that no consensus exists here. It's entirely possible that you've identified a problem that others can't see, or haven't yet encountered. I don't see it, but then maybe I'm just thick. Either way, if you think this is important, the onus is on you to demonstrate the merit of your idea and contrib/ or a github project is one way to do that (the latter has the advantage of not needing to rely on anyone else). -- Eric Evans eevans@rackspace.com --0016e6d77e595d6dff0480e844a5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

So is the current general practice to connect to a known node, e.g. by = ip address?

If so, what happens if that node is down?=C2=A0 Is the entire cluster effec= tively broken at that point?
=C2=A0
Or do clients simply maintain a list of nodes a just connect to the first a= vailable in the list?

Thanks in advance.

Cheers
Chris

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

On Wed, 2010-03-03 at 10:05 -0600, Ted= Zlatanov wrote:
> I can do a patch+ticket for this in the cor...

I don't t= hink voting is going to help. Voting doesn't do anything to
develop consensus and it seems pretty clear that no consensus exists
here.

It's entirely possible that you've identified a problem that others=
can't see, or haven't yet encountered. I don't see it, but then= maybe
I'm just thick.

Either way, if you think this is important, the onus is on you to
demonstrate the merit of your idea and contrib/ or a github project is
one way to do that (the latter has the advantage of not needing to rely
on anyone else).


--
Eric Evans
eevans@rackspace.com

--0016e6d77e595d6dff0480e844a5--