Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of ben324@gmail.com designates
 209.85.212.44 as permitted sender)
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:content-transfer-encoding;
        b=lNsjCPR+k8DUnqu9QJbWANo/Ic7iURz1fV9Iiz9DlJA9cr/edgPm5igGGKfiKKCfdh
         Bdz2fPrVsiUL1Gduf74bJyBubnWFhfwygo2TaFK8z8bepSz4wQxXbaDX3+khMh6ZeF6V
         7G3lncZZwrhbuuZQhPagl11IrtbUbLgNsBIsw=
MIME-Version: 1.0
In-Reply-To: <1C02D040F8560347822BE76ECDB76A18408F94B288@MAIL01.interprise.dk>
References: <1C02D040F8560347822BE76ECDB76A18408F94B288@MAIL01.interprise.dk>
Date: Wed, 9 Jun 2010 07:00:34 -0400
Message-ID: <AANLkTikLYlcPUctqKHHIG4_wE7sWP0oChtNVS6Cjr5hu@mail.gmail.com>
Subject: Re: Seeds and AutoBoostrap
From: Ben Browning <ben324@gmail.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

There really aren't "seed nodes" in a Cassandra cluster. When you
specify a seed in a node's configuration it's just a way to let it
know how to find the other nodes in the cluster. A node functions the
same whether it is another node's seed or not. In other words, all of
the nodes in a cluster are functionally identical - no masters, no
slaves, no seeds, etc.

So, when adding a new node to an existing cluster, you should AutoBootstrap=
 it.

On Wed, Jun 9, 2010 at 2:57 AM, Per Olesen <pol@trifork.com> wrote:
> Hi,
>
> Just a quick question on seed nodes and auto bootstrap.
>
> Am I correct in that a seed node won't be able to AutoBootstrap? And if s=
o, will a seed node newly added to an existing cluster then not take long t=
ime before it actually starts getting any work to it? I mean, if it doesn't=
 start with moving some data to itself, it will have to wait until new data=
 comes in and is determined to live on that new node.
> Correct?
>
> /Per
>
>