Copy the schema from your source keyspace to your new target keyspace,
nodetool snapshot on your source keyspace, copy the SSTable files over, do
a rolling bounce, repair, enjoy.  In my experience a rolling bounce is
easier than a nodetool refresh.

It's either that or just copy it with Spark.

On Tue, Oct 29, 2019, 11:19 AM Ankit Gadhiya <ankitgadh...@gmail.com> wrote:

> Thanks Alex. So How do I copy SSTables from 1.0 to 2.0? (Same
> SSTableLoader or any other approach?)
> Also since I've multi-node cluster - I'll have to do this on every single
> node - is there any tool or better way to execute this just from a single
> node?
>
> *Thanks & Regards,*
> *Ankit Gadhiya*
>
>
>
> On Tue, Oct 29, 2019 at 11:16 AM Alex Ott <alex...@gmail.com> wrote:
>
>> You can create all tables in new keyspace, copy SSTables from 1.0 to 2.0
>> tables & use nodetool refresh on tables in KS 2.0 to say Cassandra about
>> them.
>>
>> On Tue, Oct 29, 2019 at 4:10 PM Ankit Gadhiya <ankitgadh...@gmail.com>
>> wrote:
>>
>>> Hello Folks,
>>>
>>> Greetings!.
>>>
>>> I've a requirement in my project to setup Blue-Green deployment for
>>> Cassandra. E.x. Say My current active schema (application pointing to) is
>>> Keyspace V1.0 and for my next release I want to setup Keysapce 2.0 (with
>>> some structural changes) and all testing/validation would happen on it and
>>> once successful , App would switch connection to keyspace 2.0 - This would
>>> be generic release deployment for our project.
>>>
>>> One of the approach we thought of would be to Create keyspace 2.0 as
>>> clone from Keyspace 1.0 including data using sstableloader but this would
>>> be time consuming, also being a multi-node cluster (6+6 in each DC) - it
>>> wouldn't be very feasible to do this manually on all the nodes for multiple
>>> tables part of that keyspace. Was wondering if we have any other creative
>>> way to suffice this requirement.
>>>
>>> Appreciate your time on this.
>>>
>>>
>>> *Thanks & Regards,*
>>> *Ankit Gadhiya*
>>>
>>>
>>
>> --
>> With best wishes,                    Alex Ott
>> http://alexott.net/
>> Twitter: alexott_en (English), alexott (Russian)
>>
>

Reply via email to