>From that page:
To bootstrap a node, turn AutoBootstrap on in the configuration file,
and start it.
If you explicitly specify an InitialToken in the configuration, the
new node will bootstrap to that position on the ring. Otherwise, it
will pick a Token that will give it half the keys from the n
I saw the operations page, but didn't get what I was looking for. What
I meant by my earlier statement was that it is not clear to me who
assigns the token to a new node; if a node goes down, and another
process comes up, is (a) the token assigned to it automatically by
consensus (and the b
I'm not sure what you mean, but
http://wiki.apache.org/cassandra/Operations may clear some things up.
On Fri, Jun 11, 2010 at 7:49 PM, Sriram Srinivasan wrote:
> Fair enough. But doesn't that mean that the node that comes up has the same
> token? I suppose the answer is that the auto bootstrap pr
Fair enough. But doesn't that mean that the node that comes up has the
same token? I suppose the answer is that the auto bootstrap process is
smart enough to figure out which range needs help.
Thanks much, Jonathan.
--sriram.
On Jun 11, 2010, at 8:59 PM, Jonathan Ellis wrote:
repartitioni
repartitioning is expensive. you don't want to do it as soon as a
node goes down (which may be temporary, cassandra has no way of
knowing). so repartitioning happens when decommission is done by a
human.
On Thu, Jun 10, 2010 at 10:37 PM, Sriram Srinivasan wrote:
> I am looking at Cassandra 0.6.
I am looking at Cassandra 0.6.2's source code, and am unable to figure
out where, if at all, repartitioning happens in the case of failure.
The Gossiper's onDead message is ignored. Can someone please clarify
this for me?
