Re: Switching Snitch

2018-08-26 Thread Pradeep Chhetri
Hello Joshua Thank you very much for the replies. I will go through the tickets you sent to understand the process. Regards, Pradeep On Mon, Aug 27, 2018 at 6:15 AM, rajasekhar kommineni wrote: > Hi Pradeep, > > For changing the snitch you have decommission and add the node with new > switch a

Re: Switching Snitch

2018-08-26 Thread rajasekhar kommineni
Hi Pradeep, For changing the snitch you have decommission and add the node with new switch and updated properties files. Thanks, > On Aug 26, 2018, at 2:15 PM, Joshua Galbraith > wrote: > > Pradeep, > > Here are some related tickets that may also be helpful in understanding the > current

Re: Switching Snitch

2018-08-26 Thread Joshua Galbraith
Pradeep, Here are some related tickets that may also be helpful in understanding the current behavior of these options. * https://issues.apache.org/jira/browse/CASSANDRA-5897 * https://issues.apache.org/jira/browse/CASSANDRA-9474 * https://issues.apache.org/jira/browse/CASSANDRA-10243 * https://i

Re: Switching Snitch

2018-08-26 Thread Joshua Galbraith
Pradeep, That being said, I haven't experimented with -Dcassandra.ignore_dc=true -Dcassandra.ignore_rack=true before. The description here may be helpful: https://github.com/apache/cassandra/blob/trunk/NEWS.txt#L685-L693 I would spin up a small test cluster with data you don't care about and ver

Re: Switching Snitch

2018-08-26 Thread Joshua Galbraith
Pradeep. Right, so from that documentation is sounds like you actually have to stop all nodes in the cluster at once and bring them back up one at a time. A rolling restart won't work here. On Sun, Aug 26, 2018 at 11:46 AM, Pradeep Chhetri wrote: > Hi Joshua, > > Thank you for the reply. Sorry

Re: Switching Snitch

2018-08-26 Thread Pradeep Chhetri
Hi Joshua, Thank you for the reply. Sorry i forgot to mention that I already went through that documentation. There are few missing things regarding which I have few questions: 1) One thing which isn't mentioned there is that cassandra fails to restart when we change the datacenter name *or* rack

Re: Switching Snitch

2018-08-26 Thread Joshua Galbraith
Pradeep, it sounds like what you're proposing counts as a topology change because you are changing the datacenter name and rack name. Please refer to the documentation here about what to do in that situation: https://docs.datastax.com/en/cassandra/3.0/cassandra/operations/opsSwitchSnitch.html In

Re: Switching Snitch

2018-08-26 Thread Pradeep Chhetri
Hello everyone, Since i didn't hear from anyone, just want to describe my question again: Am i correct in understanding that i need to do following steps to migrate data from SimpleSnitch to GPFS changing datacenter name and rack name to AWS region and Availability zone respectively 1) Update th

Switching Snitch

2018-08-23 Thread Pradeep Chhetri
Hello, I am currently running a 3.11.2 cluster in SimpleSnitch hence the datacenter is datacenter1 and rack is rack1 for all nodes on AWS. I want to switch to GPFS by changing the rack name to the availability-zone name and datacenter name to region name. When I try to restart individual nodes by