Something like that, depending on your version (which you didn’t specify).
Note, though, that sstableloader is notoriously picky about the path to sstables. In particular, it really really really wants a directory structure that matches the directory structure on disk, and wants you to be at the equivalent of the parent/data_files_directory (so if you dump your sstables at /path/to/data/keyspace/table/, you’d want to run sstableloader from /path/to/data/ and provide keyspace/table/ as the location). From: Justin Sanciangco <jsancian...@blizzard.com> Reply-To: "user@cassandra.apache.org" <user@cassandra.apache.org> Date: Monday, September 19, 2016 at 5:44 PM To: "user@cassandra.apache.org" <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? >From target host sstableloader -d <target hostname> <sstable location> From: Jeff Jirsa [mailto:jeff.ji...@crowdstrike.com] Sent: Monday, September 19, 2016 4:45 PM To: 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 tools installed) via ssh/rsync and run sstableloader on the destination cluster as well. From: Justin Sanciangco <jsancian...@blizzard.com> Reply-To: "user@cassandra.apache.org" <user@cassandra.apache.org> Date: Monday, September 19, 2016 at 2:49 PM To: "user@cassandra.apache.org" <user@cassandra.apache.org> Subject: Export/Importing keyspace from a different sized cluster Hello, Assuming I can’t get ports opened from source to target cluster to run sstableloader, what methods can I use to load a single keyspace from one cluster to another cluster of different size? Appreciate the help… Thanks, Justin
smime.p7s
Description: S/MIME cryptographic signature
