Well, we ran StorageService.bulkLoad via JMX. According to http://www.datastax.com/dev/blog/bulk-loading this should have the same effect and can be done on the same machine:
"Because the sstableloader uses gossip to communicate with other nodes, if launched on the same machine that a given Cassandra node, it will need to use a different network interface than the Cassandra node. But if you want to load data from a Cassandra node, there is a simpler solution: you can use the JMX->StorageService->bulkload() call from said node." -----Ursprüngliche Nachricht----- Von: Rahul Neelakantan [mailto:ra...@rahul.be] Gesendet: Donnerstag, 31. Juli 2014 11:40 An: user@cassandra.apache.org Cc: cassandra-u...@incubator.apache.org Betreff: Re: Migration from Cassandra 1.2.5 to Cassandra 2.0.8 with changed partitioner settings You said you tried restoring a snapshot via bulk loader, did you actually run sstableloader? Rahul Neelakantan > On Jul 31, 2014, at 2:54 AM, tsi <thorsten.s...@t-systems.com> wrote: > > Well, the new Cassandra cluster is already setup with the different > partitioner settings and there are already other applications running on it. > So the task is to migrate our application data to this new cluster to > avoid setting up a dedicated Cassandra cluster just for our application. > > > > -- > View this message in context: > http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Migra > tion-from-Cassandra-1-2-5-to-Cassandra-2-0-8-with-changed-partitioner- > settings-tp7596019p7596062.html Sent from the > cassandra-u...@incubator.apache.org mailing list archive at Nabble.com.
