Running sstableloader from live Cassandra server

[Erik Forsberg <fo...@opera.com>]

Hi!

I'm looking into moving some data from one Cassandra cluster to another,
both of them running Cassandra 1.2.13 (or maybe some later 1.2 version
if that helps me avoid some fatal bug). Sstableloader will probably be
the right thing for me, and given the size of my tables, I will want to
run the sstableloader on the source cluster, but at the same time, that
source cluster needs to keep running to serve data to clients.

If I understand the docs right, this means I will have to:

1. Bring up a new network interface on each of my source nodes. No
problem, I have an IPv6 /64 to choose from :-)

2. Put a cassandra.yaml in the classpath of the sstableloader that
differs from the one in /etc/cassandra/conf, i.e. the one used by the
source cluster's cassandra, with the following:

* listen_address set to my new interface.
* rpc_address set to my new interface.
* rpc_port set as on the destination cluster (i.e. 9160)
* cluster_name set as on the destination cluster.
* storage_port as on the destination cluster (i.e. 7000)

Given the above I should be able to run sstableloader on the nodes of my
source cluster, even with source cluster cassandra daemon running.

Am I right, or did I miss anything?

Thanks,
\EF

Re: Running sstableloader from live Cassandra server

[Robert Coli <rc...@eventbrite.com>]

On Sat, Aug 16, 2014 at 2:40 AM, Erik Forsberg <fo...@opera.com> wrote:

> I will want to
> run the sstableloader on the source cluster, but at the same time, that
> source cluster needs to keep running to serve data to clients.
>

Use the on-node bulkLoad interface, which is designed for this, instead of
sstableloader, which isn't?

http://palominodb.com/blog/2012/09/25/bulk-loading-options-cassandra

"
A notable difference between "bulkLoad" and sstableloader is that
"bulkLoad" does not have sstableloader's "--ignores" option, which means
you can't tell it to ignore replica targets on failure.
"

bulkLoad there is the JMX call.

=Rob