i believe the system keyspace keeps track of the cluster topology.
even though you changed info in yaml, the system keyspace still knows
about the other nodes. remove the system keyspace files from data dir
and try again
On Fri, Oct 5, 2012 at 4:47 AM, Fredrik
wrote:
> I guess that the other nod
I guess that the other nodes still gossips about the removed node. The
node isn't removed from gossiper in the cluster until some amount of
time have elapsed. My guess is that you haven't changed the cluster_name
property in the cassandra.yaml on the removed node.
Xu, Zaili skrev 2012-09-28
To: user@cassandra.apache.org
Subject: Re: Remove node from cluster and have it run as a single node cluster
by itself
The other nodes may be trying to connect to it - it may be listed as a
seed node on the other machines?
The other nodes will be looking for it.
Change the Cluster Name in the
> The other nodes may be trying to connect to it - it may be listed as a
> seed node on the other machines?
The other nodes will be looking for it.
Change the Cluster Name in the yaml file.
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On
On Fri, 2012-09-28 at 18:53 +, Xu, Zaili wrote:
> Hi,
>
> I have an existing Cassandra Cluster. I removed a node from the cluster. Then
> I decommissioned the removed node, stopped it, updated its config so that it
> only has itself as the seed and in the cassandra-topology.properties file,
Hi,
I have an existing Cassandra Cluster. I removed a node from the cluster. Then I
decommissioned the removed node, stopped it, updated its config so that it
only has itself as the seed and in the cassandra-topology.properties file, even
deleted the data, commitlog, and saved_caches. But as s
