On Mon, Apr 7, 2014 at 1:41 PM, Brandon McCauslin wrote:
> 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 dat
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 10:48 AM, Brandon McCauslin 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 assum
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
Pro
I would go with option 1.
I think it is the safer of the two options, involves less work and if
something were to go wrong mid migration you can remove the second DC from
your keyspace replication and have a clean break. SimpleStrategy will work
across DCs. It is generally advised to not use it ac
We're currently running a small 5 node 2.0.5 cluster in a single datacenter
using the SimpleStrategy replication strategy with replication factor of 3.
We want to migrate our data from our current datacenter to a new
datacenter, without incurring any downtime or data loss. There is no plan
to mai
