Rob, If I read your response in that 1st URL correctly, it seems changing both the snitch and replication strategy at the same time is not advisable and could lead to partial data loss. Is your suggestion of dumping an reloading the data into the new cluster still recommended for these situations?
On Mon, Apr 7, 2014 at 2:09 PM, Robert Coli <[email protected]> wrote: > On Mon, Apr 7, 2014 at 10:48 AM, Brandon McCauslin <[email protected]>wrote: > >> Thanks for the confirmation on the approach. The new dc is not yet >> ready, but while I'm waiting I was thinking about updating the existing >> dc's replication strategy from "SimpleStrategy" to >> "NetworkTopologyStrategy". I also assume I'll need to update my snitch >> from the current SimpleSnitch to PropertyFileSnitch. Here's the steps I'm >> thinking: >> > > Here's a brief explication of how this process works and can be made > safe/testable : > > > http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Ec2Snitch-amp-Other-snitches-td6196494.html > > Consider whether you actually want a rack aware Snitch : > > https://issues.apache.org/jira/browse/CASSANDRA-3810 > > If you do, consider using the Gossiping Property File Snitch : > > https://issues.apache.org/jira/browse/CASSANDRA-1974 > > =Rob > >
