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
> wrote:
>
&g
ome 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
I only did in-place conversions from DSE to Apache Cassandra, but after
altering the replication scheme I later dropped those keyspaces after the
fact. You can keep them there on Apache, they'll just be fallow and taking
up space. Not even that much space anyway. Don't forget to change the
authe
