On Wed, Aug 13, 2014 at 7:28 AM, Rahul Gupta
wrote:
> Found the issue and the solution.
>
>
> 1. Do not clone existing Cassandra node and use it as additional
> node. Always start with a fresh machine which never had any Cassandra
> installed in it.
>
>
> 2. Fix the host id in the
prohibited. If you have received this communication in error, please
immediately notify the sender and destroy the original message.
From: Jens Rantil [mailto:jens.ran...@tink.se]
Sent: Friday, August 08, 2014 1:09 PM
To: user@cassandra.apache.org
Cc: user@cassandra.apache.org
Subject: Re: Host ID
Rahul,
I'm pretty sure it's preferable to clean all files and directories in
/var/log/cassandra before starting up the new Cassandra node. This will make it
start on a clean slate resetting all state from previous node.
Cheers,
Jens
—
Sent from Mailbox
On Fri, Aug 8, 2014 at 6:21 PM, Rahu
I have a 3 node Cassandra Cluster. Using DataStax Enetrprise v4.5.1 on VMWare.
I am adding 1 new node to this cluster for running Analytics workload.
So I cloned existing one of the Cassandra VMs, changed the hostname, restarted
VMs, then updated Cassandra.yaml file and restarted Cassandra.
172.1
