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:ankitgadh...@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 <lapostadiser...@gmail.com<mailto:lapostadiser...@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 <paul.carlu...@gmail.com<mailto:paul.carlu...@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 > <ankitgadh...@gmail.com<mailto: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<mailto: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<mailto: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/<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-unsubscr...@cassandra.apache.org<mailto:user-unsubscr...@cassandra.apache.org> For additional commands, e-mail: user-h...@cassandra.apache.org<mailto:user-h...@cassandra.apache.org>
