he data into the new DC and susbsequently alter the
>> keyspace to replicate from the older DC.
>>
>> Cheers
>> Jan
>>
>>
>> ------------
>> On Thu, 4/21/16, Jens Rantil wrote:
>>
>> Subject: Re: Alternat
e older DC.
>
> Cheers
> Jan
>
>
>
> On Thu, 4/21/16, Jens Rantil wrote:
>
> Subject: Re: Alternative approach to setting up new DC
> To: user@cassandra.apache.org
> Date: Thursday, April 21, 2016, 9:00 AM
>
> Hi,
rote:
Subject: Re: Alternative approach to setting up new DC
To: user@cassandra.apache.org
Date: Thursday, April 21, 2016, 9:00 AM
Hi,
I never got
any response here, but just wanted to share that I went to a
Cassandra meet-up in Stockholm yesterday where I talked to
two knowledgable Cassandra pe
Hi,
I never got any response here, but just wanted to share that I went to a
Cassandra meet-up in Stockholm yesterday where I talked to two knowledgable
Cassandra people that verified that the approach below should work. The
most important thing is that the backup must be fully imported before
gc_
Hi,
I am provisioning a new datacenter for an existing cluster. A rather shaky
VPN connection is hindering me from making a "nodetool rebuild" bootstrap
on the new DC. Interestingly, I have a full fresh database snapshot/backup
at the same location as the new DC (transferred outside of the VPN). I
