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
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 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
: Gary Dusbabek [mailto:gdusba...@gmail.com]
Sent: Friday, June 11, 2010 2:58 AM
To: dev@cassandra.apache.org
Subject: Re: New keyspace loading creates 'master'
On Thu, Jun 10, 2010 at 17:16, Ronald Park wrote:
> What we found was that, if the node on which we originally installed t
On Thu, Jun 10, 2010 at 17:16, Ronald Park wrote:
> What we found was that, if the node on which we originally installed the
> keyspace was down when a new node is added, the new node does not get the
> keyspace schema. In some regards, it is now the 'master', at least in
> distributing the keysp
Hi,
We've been fiddling around with a small Cassandra cluster, bringing
nodes up and down, to get a feel for how things are replicated and how
spinning up a new node works (before having to learn it live :). We are
using the trunk because we want to use the expiration feature. Along
with th
