I can confirm that not all nodes receive schema, not only new, but some old
also, while old one were dead on time of keyspace creation and upon return have
not received an update. Sometime even all nodes running fine, not all have
received schema update.
Viktor
-Original Message-
From:
I've filed this as
https://issues.apache.org/jira/browse/CASSANDRA-1182. I've created
steps to reproduce based on your email and placed them in the ticket
description. Can you confirm that I've described things correctly?
Gary.
On Thu, Jun 10, 2010 at 17:16, Ronald Park wrote:
> Hi,
>
> We've
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 was unable to duplicate this problem using a 3 node cluster. Here
were my steps:
1. bring up a seed node, give it a schema using loadSchemaFromYaml
2. bring up a second node. it received schema from the seed node.
3. bring the seed node down.
4. bring up a third node, but set it's seed to be the
I've been trying a number of combinations of starting/stopping machines
with and without various seeds and I can't recreate the problem now. I
strongly suspect it was because we were trying to use the
DatacenterShardStrategy code. Between changing snitches and shard
classes, we haven't been a
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
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
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
