Thank you guys! Much appreciated.
Leaving the snitch aside for a moment, we can fix this either before or
after the migration.
I understand I should prefer adding a new DC rather than
extending/shrinking my current (and only) DC. Correct?
Thanks,
On Fri, Jun 8, 2018 at 2:22 AM, kurt greaves
>
> I meant migrating to gosspsnitch during adding new dc. New dc will be
> empty so all the data will be streamed based on snitch property chosen
Should work fine on the new DC, as long as the original DC is using a
snitch that supports datacenters - then just don't mix and match snitches
I meant migrating to gosspsnitch during adding new dc. New dc will be empty so
all the data will be streamed based on snitch property chosen
Sent from my iPhone
> On Jun 7, 2018, at 12:23 PM, Jeff Jirsa wrote:
>
> I don't know about "new snitch protocol" (there is no snitch protocol), but
>
I don't know about "new snitch protocol" (there is no snitch protocol), but
in the case of ec2snitch and gossipingpropertyfilesnitch (do not
extrapolate this to any other combination), you can switch them 1:1 before
the move, and everything should be fine, as long as care is taken to make
the
Jeff,
In this case, if Riccardo is adding new DC, then he can pickup new snitch
protocol right?
On Thu, Jun 7, 2018 at 12:15 PM, Jeff Jirsa wrote:
>
>
>
> On Thu, Jun 7, 2018 at 9:12 AM, Nitan Kainth
> wrote:
>
>> Riccardo,
>>
>> Simplest method can be is to add VPC as an additional
On Thu, Jun 7, 2018 at 9:12 AM, Nitan Kainth wrote:
> Riccardo,
>
> Simplest method can be is to add VPC as an additional datacenter to
> existing cluster; once New DC has synced up all data, just switch over your
> application. Only caveat is that there should be enough network bandwidth
>
Riccardo,
Simplest method can be is to add VPC as an additional datacenter to
existing cluster; once New DC has synced up all data, just switch over your
application. Only caveat is that there should be enough network bandwidth
between EC2 and VPC.
Horizontal scaling will help to some extent.
