seriously, If you change the cluster name in cassandra.yaml they won't
join.
On Thu, Aug 11, 2011 at 12:31 PM, Ashley Martens wrote:
> No shared seeds. Downright freaky.
>
>
--
http://twitter.com/tjake
No shared seeds. Downright freaky.
There is nothing solandra specific that would cause this. There were no shared
seeds?
On Aug 10, 2011, at 6:24 PM, Ashley Martens wrote:
> Nope. Clean system.
>
> On Wed, Aug 10, 2011 at 3:22 PM, Nick Bailey wrote:
> Did you perhaps start up the second cluster with data from the test
> clu
Nope. Clean system.
On Wed, Aug 10, 2011 at 3:22 PM, Nick Bailey wrote:
> Did you perhaps start up the second cluster with data from the test
> cluster? If you accidentally copied the system tables over, cassandra
> would recognize the saved tokens/ips from the test cluster and attempt
> to goss
Did you perhaps start up the second cluster with data from the test
cluster? If you accidentally copied the system tables over, cassandra
would recognize the saved tokens/ips from the test cluster and attempt
to gossip with them.
On Wed, Aug 10, 2011 at 5:19 PM, Ashley Martens wrote:
> I just had
I just had a strange issue with a solandra ring. We had a two node test
cluster running in one data center and then started up a second 5 node
cluster in another data center. The seed in the first DC was in that DC and
the seed in the second DC was in the second DC, so the two rings should not
have
