You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Ankit Gadhiya <an...@gmail.com> on 2019/10/29 15:10:03 UTC
Keyspace Clone in Existing Cluster
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*
RE: Keyspace Clone in Existing Cluster
Posted by "ZAIDI, ASAD" <az...@att.com>.
If you’re planning to restore snapshot to target keyspace in same cluster – you can:
1. Take snapshot and copy snapshots to shared volume like NFS share so later you can load sstables using sstables loader from single node.
2. Make sure you create target keyspace and tables (without data) only structure BEFORE loading with sstalbes. Usually when you take snapshot, a file named schema.cql is created . you can create schema object with this script.
3. The name of target kespace/tables are import – they have to match with sstableloader input arguments.
4. Then run sstableloader – you’ll get data/sstables loaded in bulk and streamed to all the nodes in cluster.
Thanks/Asad
From: Ankit Gadhiya [mailto:ankitgadhiya@gmail.com]
Sent: Tuesday, October 29, 2019 1:20 PM
To: user@cassandra.apache.org
Subject: Re: Keyspace Clone in Existing Cluster
Thanks folks for your responses but still haven't found concrete solution for this.
Thanks & Regards,
Ankit Gadhiya
On Tue, Oct 29, 2019 at 2:15 PM Sergio Bilello <la...@gmail.com>> wrote:
Rolling bounce = Rolling repair per node? Would not it be easy to be scheduled with Cassandra Reaper?
On 2019/10/29 15:35:42, Paul Carlucci <pa...@gmail.com>> wrote:
> 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 <an...@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 <al...@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 <an...@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/<https://urldefense.proofpoint.com/v2/url?u=http-3A__alexott.net_&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=FsmDztdsVuIKml8IDhdHdg&m=AsDdSaFLGjjyZQ4BrrOC-gtdBcLywl0sGnxpDeJpJjc&s=5kCeuojO_jd-gBt6K5k1Dus9wM6FzFYjqSheE6le4C0&e=>
> >> Twitter: alexott_en (English), alexott (Russian)
> >>
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org<ma...@cassandra.apache.org>
For additional commands, e-mail: user-help@cassandra.apache.org<ma...@cassandra.apache.org>
Re: Keyspace Clone in Existing Cluster
Posted by Ankit Gadhiya <an...@gmail.com>.
Thanks folks for your responses but still haven't found concrete solution
for this.
*Thanks & Regards,*
*Ankit Gadhiya*
On Tue, Oct 29, 2019 at 2:15 PM Sergio Bilello <la...@gmail.com>
wrote:
> Rolling bounce = Rolling repair per node? Would not it be easy to be
> scheduled with Cassandra Reaper?
> On 2019/10/29 15:35:42, Paul Carlucci <pa...@gmail.com> wrote:
> > 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 <an...@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 <al...@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 <ankitgadhiya@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)
> > >>
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: user-help@cassandra.apache.org
>
>
Re: Keyspace Clone in Existing Cluster
Posted by Sergio Bilello <la...@gmail.com>.
Rolling bounce = Rolling repair per node? Would not it be easy to be scheduled with Cassandra Reaper?
On 2019/10/29 15:35:42, Paul Carlucci <pa...@gmail.com> wrote:
> 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 <an...@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 <al...@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 <an...@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)
> >>
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
For additional commands, e-mail: user-help@cassandra.apache.org
Re: Keyspace Clone in Existing Cluster
Posted by Paul Carlucci <pa...@gmail.com>.
When in doubt, repair. Nodetool snapshot won't be perfectly consistent
across all the nodes anyway since you're snapshotting on each node
individually.
On Tue, Oct 29, 2019, 8:31 PM Ankit Gadhiya <an...@gmail.com> wrote:
> Thanks Paul. This is interesting.
> So, anything I need to do after cp? - nodetool repair?
> Also I am assuming I need to be doing this exercise on all the nodes of
> the cluster - right?
> Any suggestion to automate this or do it just from a single node?
>
>
> — Ankit Gadhiya
>
> On Tue, Oct 29, 2019 at 11:21 PM Paul Carlucci <pa...@gmail.com>
> wrote:
>
>> Straight up Unix cp command, make sure you're in the right directory. If
>> you try to use schema.cql then you're going to have to massage it somewhat
>> due to keyspace name differences and schema changes over time. You'll see
>> what I mean if you've got some.
>>
>> It goes without saying that you're gonna want to try this in non-prod
>> first. On a positive note you'll be learning some stuff they don't quite
>> teach in Datastax Academy!
>>
>> On Tue, Oct 29, 2019, 8:39 AM Ankit Gadhiya <an...@gmail.com>
>> wrote:
>>
>>> Thanks Paul.
>>>
>>> Copy SSTable - How? Using SSTableLoader or some other mechanism.
>>>
>>>
>>> *Thanks & Regards,*
>>> *Ankit Gadhiya*
>>>
>>>
>>>
>>> On Tue, Oct 29, 2019 at 11:36 AM Paul Carlucci <pa...@gmail.com>
>>> wrote:
>>>
>>>> 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 <an...@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 <al...@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 <an...@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)
>>>>>>
>>>>> --
> *Thanks & Regards,*
> *Ankit Gadhiya*
>
>
Re: Keyspace Clone in Existing Cluster
Posted by Ankit Gadhiya <an...@gmail.com>.
Thanks Paul. This is interesting.
So, anything I need to do after cp? - nodetool repair?
Also I am assuming I need to be doing this exercise on all the nodes of the
cluster - right?
Any suggestion to automate this or do it just from a single node?
— Ankit Gadhiya
On Tue, Oct 29, 2019 at 11:21 PM Paul Carlucci <pa...@gmail.com>
wrote:
> Straight up Unix cp command, make sure you're in the right directory. If
> you try to use schema.cql then you're going to have to massage it somewhat
> due to keyspace name differences and schema changes over time. You'll see
> what I mean if you've got some.
>
> It goes without saying that you're gonna want to try this in non-prod
> first. On a positive note you'll be learning some stuff they don't quite
> teach in Datastax Academy!
>
> On Tue, Oct 29, 2019, 8:39 AM Ankit Gadhiya <an...@gmail.com>
> wrote:
>
>> Thanks Paul.
>>
>> Copy SSTable - How? Using SSTableLoader or some other mechanism.
>>
>>
>> *Thanks & Regards,*
>> *Ankit Gadhiya*
>>
>>
>>
>> On Tue, Oct 29, 2019 at 11:36 AM Paul Carlucci <pa...@gmail.com>
>> wrote:
>>
>>> 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 <an...@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 <al...@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 <an...@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)
>>>>>
>>>> --
*Thanks & Regards,*
*Ankit Gadhiya*
Re: Keyspace Clone in Existing Cluster
Posted by Paul Carlucci <pa...@gmail.com>.
Straight up Unix cp command, make sure you're in the right directory. If
you try to use schema.cql then you're going to have to massage it somewhat
due to keyspace name differences and schema changes over time. You'll see
what I mean if you've got some.
It goes without saying that you're gonna want to try this in non-prod
first. On a positive note you'll be learning some stuff they don't quite
teach in Datastax Academy!
On Tue, Oct 29, 2019, 8:39 AM Ankit Gadhiya <an...@gmail.com> wrote:
> Thanks Paul.
>
> Copy SSTable - How? Using SSTableLoader or some other mechanism.
>
>
> *Thanks & Regards,*
> *Ankit Gadhiya*
>
>
>
> On Tue, Oct 29, 2019 at 11:36 AM Paul Carlucci <pa...@gmail.com>
> wrote:
>
>> 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 <an...@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 <al...@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 <an...@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)
>>>>
>>>
Re: Keyspace Clone in Existing Cluster
Posted by Ankit Gadhiya <an...@gmail.com>.
Thanks Paul.
Copy SSTable - How? Using SSTableLoader or some other mechanism.
*Thanks & Regards,*
*Ankit Gadhiya*
On Tue, Oct 29, 2019 at 11:36 AM Paul Carlucci <pa...@gmail.com>
wrote:
> 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 <an...@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 <al...@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 <an...@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)
>>>
>>
Re: Keyspace Clone in Existing Cluster
Posted by Paul Carlucci <pa...@gmail.com>.
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 <an...@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 <al...@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 <an...@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)
>>
>
Re: Keyspace Clone in Existing Cluster
Posted by Ankit Gadhiya <an...@gmail.com>.
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 <al...@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 <an...@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)
>
Re: Keyspace Clone in Existing Cluster
Posted by Alex Ott <al...@gmail.com>.
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 <an...@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)