SimpleSnitch is not rack aware. You would want to choose seed nodes and then not change them. Seed nodes apparently don’t bootstrap. All nodes need the same seeds in the yaml file. Here is more info: http://www.datastax.com/documentation/cassandra/2.0/cassandra/initialize/initializeSingleDS.html
Sean Durity – Cassandra Admin, Big Data Team To engage the team, create a request<https://portal.homedepot.com/sites/bigdata/SitePages/Big%20Data%20Engagement%20Request.aspx> From: Batranut Bogdan [mailto:batra...@yahoo.com] Sent: Tuesday, February 17, 2015 3:28 PM To: user@cassandra.apache.org; reynald.bourtembo...@esrf.fr Subject: Re: Adding new node to cluster Hello, I use SimpleSnitch. All the nodes are in the sane datacenter. Not sure if all are in the same rack. On Tuesday, February 17, 2015 8:53 PM, "sean_r_dur...@homedepot.com<mailto:sean_r_dur...@homedepot.com>" <sean_r_dur...@homedepot.com<mailto:sean_r_dur...@homedepot.com>> wrote: What snitch are you using? You may need to do some work on your topology file (or rackdc) to make sure you have the topology you want. Also, it is possible you may need to restart OpsCenter agents and/or your browser to see the nodes represented properly in OpsCenter. Sean Durity – Cassandra Admin, Home Depot From: Batranut Bogdan [mailto:batra...@yahoo.com] Sent: Tuesday, February 17, 2015 10:20 AM To: user@cassandra.apache.org<mailto:user@cassandra.apache.org>; reynald.bourtembo...@esrf.fr<mailto:reynald.bourtembo...@esrf.fr> Subject: Re: Adding new node to cluster Hello, I know that UN is good, but what troubles me is the addition of the own node's ip in it's yaml seeds section. On Tuesday, February 17, 2015 3:40 PM, Reynald Bourtembourg <reynald.bourtembo...@esrf.fr<mailto:reynald.bourtembo...@esrf.fr>> wrote: Hi Bogdan In nodetool status: * UJ: means your node is Up and Joining * UN: means your node is Up and in Normal state UN in nodetool is good ;-) On 17/02/2015 13:56, Batranut Bogdan wrote: Hello all, I have an existing cluster. When adding a new node, I saw that Opscenter saw the node in an unknown cluster. In the yaml, the cluster name is the same. So i have stopped the node and added it's ip address in the list of seeds. Now Opscenter sees my node. But nodetool status now sees it as UN, instead of UJ when it first started. One other mension is that even if I stop the node, remove it's ip from the list of seeds, Opscenter sees the node in the known clustre but nodetool sees it as UN. I am not sure what the implications of adding a node's ip in it's seed list are and I think that for the existing nodes I have might done the same. Eg. started with it's ip in the seed list but after removing it and having to restart the nodes for whatever reason, I did not see any changes. Is my cluster ok, or what do I need to do to bring the cluster to a good state? Thank you. ________________________________ The information in this Internet Email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this Email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this Email are subject to the terms and conditions expressed in any applicable governing The Home Depot terms of business or client engagement letter. The Home Depot disclaims all responsibility and liability for the accuracy and content of this attachment and for any damages or losses arising from any inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other items of a destructive nature, which may be contained in this attachment and shall not be liable for direct, indirect, consequential or special damages in connection with this e-mail message or its attachment. ________________________________ The information in this Internet Email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this Email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this Email are subject to the terms and conditions expressed in any applicable governing The Home Depot terms of business or client engagement letter. The Home Depot disclaims all responsibility and liability for the accuracy and content of this attachment and for any damages or losses arising from any inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other items of a destructive nature, which may be contained in this attachment and shall not be liable for direct, indirect, consequential or special damages in connection with this e-mail message or its attachment.
