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 wrote:
> Thanks Paul. This is interesting.
> So, anything I need to do after cp? - nodetool
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
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
. 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
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
wrote:
> Rolling bounce = Rolling repair per node? Would not it be easy to be
> scheduled with Cassandra Reaper?
> On
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 wrote:
> Copy the schema from your source keyspace to your new target keyspace,
> nodetool snapshot on your source keyspace, copy the SSTable files over,
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
wrote:
> Copy the schema from your source keyspace to your new target keyspace,
> nodetool snapshot on your source keyspace, copy
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
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
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
wrote:
> Hello Folks,
>
> Greetings!.
>
> I've a requirement in my project to setup Blue-Green
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
11 matches
Mail list logo
