Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 22637 invoked from network); 8 Dec 2010 01:31:05 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 8 Dec 2010 01:31:05 -0000 Received: (qmail 86466 invoked by uid 500); 8 Dec 2010 01:31:03 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 86441 invoked by uid 500); 8 Dec 2010 01:31:03 -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 86433 invoked by uid 99); 8 Dec 2010 01:31:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Dec 2010 01:31:03 +0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jbellis@gmail.com designates 209.85.160.44 as permitted sender) Received: from [209.85.160.44] (HELO mail-pw0-f44.google.com) (209.85.160.44) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Dec 2010 01:30:56 +0000 Received: by pwi7 with SMTP id 7so187922pwi.31 for ; Tue, 07 Dec 2010 17:30:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=KlyFh884hMUVcJTN7SHIytJh4ToCIgqWtNzH4g1pB8A=; b=siPr6tjpaybu6aGy8n/icH8lMSFzGIXhMUDQijsTDu2VBHpIW0G3E+K6yYaqpAZGt2 1co703REfZOVg/dQQiYfJpwZnzkvlT0h2p7qdGUP4eJVswAjaPkHU056vvZCESKzxv9T 9BiCXW/xyR4ASosFwmSCKroUj1ssPRIHnwv0c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=VeLZGd7L4ciEQbVO4aLRNBpJAUmxNmkdPsgVEn589gWanVP1L2hsZu/6v8DY0dwOIZ 30LIEO/fsROcA28Tyu8WE7Bkyxk5eeaJz9uHkshAGHbkBJALFvmXC517bWAQEa+uQst0 +CxvmwvHTPF6dTjcvqK8aatGUObflvumh4Dj8= MIME-Version: 1.0 Received: by 10.143.5.7 with SMTP id h7mr1795860wfi.45.1291771834645; Tue, 07 Dec 2010 17:30:34 -0800 (PST) Received: by 10.142.224.15 with HTTP; Tue, 7 Dec 2010 17:30:34 -0800 (PST) In-Reply-To: References: Date: Tue, 7 Dec 2010 19:30:34 -0600 Message-ID: Subject: Re: If one seed node crash, how can I add one seed node? From: Jonathan Ellis To: user Content-Type: multipart/alternative; boundary=001636e90fd755bf240496dc11cd X-Virus-Checked: Checked by ClamAV on apache.org --001636e90fd755bf240496dc11cd Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable "Two seeds per datacenter" is my rule of thumb. On Tue, Dec 7, 2010 at 3:07 PM, Eric Gilmore wrote: > What would comprise a sane and reasonably balanced list? Should there be= a > certain proportion of seeds per total nodes? Any other considerations > besides a) list must be identical on all nodes and b) you can't > auto-bootstrap a seed node? > > I'm new to thinking about this setting, but it sounds like this discussio= n > may be approaching some best-practice guidelines. > > > On Tue, Dec 7, 2010 at 1:01 PM, Jonathan Ellis wrote: > >> The gossip-to-seed each round is to prevent cluster partitions, so if >> you're following correct procedure and making every node's seed list >> identical, then any potential new nodes gossiping to one of the old seed= s >> means it is still harmless for old nodes not to gossip to the new one un= til >> the next restart. >> >> >> On Tue, Dec 7, 2010 at 2:10 PM, Aaron Morton wr= ote: >> >>> Ryan, >>> I've not checked with the code but the wiki docs for the Gossip Protoco= l >>> say it makes use of the seed list. >>> http://wiki.apache.org/cassandra/ArchitectureGossip >>> >>> During each gossip round a node will try to gossip to one seed node. >>> >>> Which made me think keeping the list sane and reasonably balanced was a >>> good idea. Obviously would not matter too much on a small cluster thoug= h. >>> >>> Aaron >>> >>> >>> On 08 Dec, 2010,at 07:16 AM, Ryan King wrote: >>> >>> Note that there's not really anything special about the seed node and i= ts >>> all relative=96 the cluster doesn't necessarily have to agreed on who t= he >>> seeds are. >>> >>> So, to bring up a new node to replace the old seed, just set the new >>> node's seed to any existing node in the system. After that you can go b= ack >>> and make the setting consistent across the cluster. >>> >>> -ryan >>> >>> On Tue, Dec 7, 2010 at 7:01 AM, Nick Bailey wrote: >>> >>>> Yes, cassandra only reads the configuration when it starts up. However >>>> seed nodes are only used when a node starts. After that they aren't ne= eded. >>>> There should be no reason to restart your cluster after adding a seed = node >>>> to your cluster. >>>> >>>> >>>> >>>> On Tue, Dec 7, 2010 at 2:09 AM, aaron morton = wrote: >>>> >>>>> You will need to restart the nodes for them to pickup changes in >>>>> cassandra.yaml >>>>> >>>>> >>>>> Aaron >>>>> >>>>> >>>>> On 7 Dec 2010, at 16:32, lei liu wrote: >>>>> >>>>> Thanks Nick. >>>>> >>>>> After I add the new node as seed node in the configuration for all of >>>>> my nodes, do I need to restart all of my nodes? >>>>> >>>>> 2010/12/7 Nick Bailey >>>>> >>>>>> The node can be set as a seed node at any time. It does not need to = be >>>>>> a seed node when it joins the cluster. You should remove it as a see= d node, >>>>>> set autobootstrap to true and let it join the cluster. Once it has j= oined >>>>>> the cluster you should add it as a seed node in the configuration fo= r all of >>>>>> your nodes. >>>>>> >>>>>> >>>>>> >>>>>> On Mon, Dec 6, 2010 at 9:59 AM, lei liu wrote: >>>>>> >>>>>>> Thank Jonathan for your reply. >>>>>>> >>>>>>> How can I bootstrap the node into cluster, I know if the node is >>>>>>> seed node, I can't set AutoBootstrap to true. >>>>>>> >>>>>>> 2010/12/6 Jonathan Ellis >>>>>>> >>>>>>>> set it as a seed _after_ bootstrapping it into the cluster. >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Dec 6, 2010 at t5:01 AM, lei liu >>>>>>>> wrote: >>>>>>>> > After one seed node crash, I want to add one node as seed node, = I >>>>>>>> set >>>>>>>> > auto_bootstrap to true, but the new node don't migrate data from >>>>>>>> other >>>>>>>> > node s. >>>>>>>> > >>>>>>>> > How can I add one new seed node and let the node to migrate data >>>>>>>> from other >>>>>>>> > nodes? >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > Thanks, >>>>>>>> > >>>>>>>> > LiuLei >>>>>>>> > >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Jonathan Ellis >>>>>>>> Project Chair, Apache Cassandra >>>>>>>> co-founder of Riptano, the source for professional Cassandra suppo= rt >>>>>>>> http://riptano.com >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>> >>> >> >> >> -- >> Jonathan Ellis >> Project Chair, Apache Cassandra >> co-founder of Riptano, the source for professional Cassandra support >> http://riptano.com >> > > > > -- > *Eric Gilmore > * > Consulting Technical Writer > Riptano, Inc. > Ph: 510 684 9786 (cell) > > --=20 Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com --001636e90fd755bf240496dc11cd Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable "Two seeds per datacenter" is my rule of thumb.

On Tue, Dec 7, 2010 at 3:07 PM, Eric Gilmore <eric@riptano.com> wrote:
What would compri= se a sane and reasonably balanced list?=A0 Should there be a certain propor= tion of seeds per total nodes?=A0 Any other considerations besides a) list = must be identical on all nodes and b) you can't auto-bootstrap a seed n= ode?

I'm new to thinking about this setting, but it sounds like this dis= cussion may be approaching some best-practice guidelines.


On Tue, Dec 7, 2010 at 1= :01 PM, Jonathan Ellis <jbellis@gmail.com> wrote:
The gossip-to-see= d each round is to prevent cluster partitions, so if you're following c= orrect procedure and making every node's seed list identical, then any = potential new nodes gossiping to one of the old seeds means it is still har= mless for old nodes not to gossip to the new one until the next restart.


On Tue, Dec 7, 2010 at 2:10 PM, Aaron Morton= <aaron@thelastpickle.com> wrote:
Ryan,=A0
I've not checked with the code but the wik= i docs for the Gossip Protocol say it makes use of the seed list.=A0= http://wiki.apache.org/cassandra/ArchitectureGossip

During each gossip round a node will try to = gossip to one seed node.=A0

Which made me think ke= eping the list sane and reasonably=A0balanced was a good idea. Obviously wo= uld not matter too much on a small cluster though.=A0

Aaron


On 08 Dec, 2010,at 07:16 AM, Ryan King <= ryan@twitter.com&= gt; wrote:

Note that there's not rea= lly anything special about the seed node and its all relative=96 the cluste= r doesn't necessarily have to agreed on who the seeds are.

So, to bring up a new node to replace the old seed, just set the new n= ode's seed to any existing node in the system. After that you can go ba= ck and make the setting consistent across the cluster.

-ryan

On Tue, Dec 7, = 2010 at 7:01 AM, Nick Bailey <nick@riptano.com> wrote:
Yes, cassandra only reads the configuration when it starts up. However seed= nodes are only used when a node starts. After that they aren't needed.= There should be no reason to restart your cluster after adding a seed node= to =A0your cluster.



On Tue, Dec 7, 2010 at 2:09 AM, aaron morton= <aaron@thelastpickle.com> wrote:
You will need to restart the nodes fo= r them to pickup changes in cassandra.yaml


Aaron


On 7 Dec 2010, at 16:32, lei liu wrote:

Thanks 3D""Nick.=

After I add the new node as seed node in the configuration for all = of my nodes, do I need to restart all of my nodes?

2010/12/7 Nick Bailey <= nick@riptano.com&= gt;
The node can be set as a seed node at any time. It does not need to be a se= ed node when it joins the cluster. You should remove it as a seed node, set= autobootstrap to true and let it join the cluster. Once it has joined the = cluster you should add it as a seed node in the configuration for all of yo= ur nodes.



On Mon, Dec 6, 2010 at 9:59 AM, lei liu <= liulei412@gmail.com> wrote:
Thank Jonathan for your reply.

How=A0 can I bootstrap the node into = cluster, I know if the node is seed node, I can't set AutoBootstrap to = true.

2010/12/6 Jonathan Ellis <jbellis= @gmail.com>
set it as a = seed _after_ bootstrapping it into the cluster.


On Mon, Dec 6, 2010 at t5:01 AM, lei liu <liulei412@gmail.com> wrote:
> After one seed node crash, I want to add one node as seed node, I set<= br> > auto_bootstrap to true, but the new node don't migrate data from o= ther
> node s.
>
> How can I add one new seed node and let the node to migrate data from = other
> nodes?
>
>
>
> Thanks,
>
> LiuLei
>



--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com









--
Jonathan Ellis
Proj= ect Chair, Apache Cassandra
co-founder of Riptano, the source for profes= sional Cassandra support
http://riptano.com



--
Eric Gilmore
Consulting Technical Writer
=
Riptano, Inc.
Ph: 510 684 9786=A0 (cell)




--
Jonathan EllisProject Chair, Apache Cassandra
co-founder of Riptano, the source for = professional Cassandra support
http://rip= tano.com
--001636e90fd755bf240496dc11cd--