From: Justin Sanciangco
[mailto:jsancian...@blizzard.com]
Sent: Monday, September 19, 2016 6:20 PM
To: user@cassandra.apache.org
Subject: RE: Export/Importing keyspace from a different sized cluster I am
running cqlsh 5.0.1 | Cassandra 2.1.11.969 | DSE 4.8.3 | CQL spec 3.2.1 |
Doing the below
filesystem, etc.
Mike
*From:* Justin Sanciangco [mailto:jsancian...@blizzard.com]
*Sent:* Monday, September 19, 2016 6:20 PM
*To:* user@cassandra.apache.org
*Subject:* RE: Export/Importing keyspace from a different sized cluster
I am running
cqlsh 5.0.1 | Cassandra 2.1.11.969 | DSE 4.8.3
a [mailto:jeff.ji...@crowdstrike.com]
Sent: Monday, September 19, 2016 4:45 PM
To: user@cassandra.apache.org<mailto:user@cassandra.apache.org>
Subject: Re: Export/Importing keyspace from a different sized cluster
You can ship the sstables to the destination (or any other server with
Cassandra binary
uot;
Date: Monday, September 19, 2016 at 5:44 PM
To: "user@cassandra.apache.org"
Subject: RE: Export/Importing keyspace from a different sized cluster
So if I rsync the the sstables say from source node 1 and source node 2 to
target node 1. Would I just run the command like this?
Subject: Re: Export/Importing keyspace from a different sized cluster
You can ship the sstables to the destination (or any other server with
Cassandra binary tools installed) via ssh/rsync and run sstableloader on the
destination cluster as well.
From: Justin Sanciangco
mailto:jsancian
You can ship the sstables to the destination (or any other server with
Cassandra binary tools installed) via ssh/rsync and run sstableloader on the
destination cluster as well.
From: Justin Sanciangco
Reply-To: "user@cassandra.apache.org"
Date: Monday, September 19, 2016 at 2:49 PM
To: "
CQLSH COPY FROM / COPY TO? There are some significant performance
improvements in recent versions:
https://issues.apache.org/jira/browse/CASSANDRA-11053
On Tue, 20 Sep 2016 at 07:49 Justin Sanciangco
wrote:
> Hello,
>
>
>
> Assuming I can’t get ports opened from source to target cluster to run
>
