To further clarify @carl.mueller's comments above, it would appear that
both the initial jump in metrics (and subsequent drop) was app-related, not
cassandra related.
On Tue, Jun 25, 2019 at 1:45 PM Carl Mueller
wrote:
> Nevermind, it would appear once we looked further out on the metrics there
Hi Voytek,
We moved a large number of clusters from Rackspace to Google, doing it in a
similar way to you are suggesting, so to answer your questions:
1) We created the nodes first with seeds from just the original datacenters,
then updated the seed list to include seeds from the new DC afterwa
Expanding on number 4 below:
I'm not quite sure what the easiest course of action might be. Currently
the 4 existing nodes listen on private IPs and seeds are set to internal
DNS names. Is setting broadcast_address to their public IPs and restarting
a viable solution?
I'm trying to minimize chang
I started an higher-level thread years ago about moving a cluster by
expanding from 1 to 2 datacenters, replicating over, then decommissioning
the original DC. Corporate plans being what they are, we're finally getting
into this; I'm largely following the writeup here:
https://docs.datastax.com/en/
