he 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
>
-
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
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 wrote:
>
> Well, the new Cassandra cluster is already setup with the different
> partitioner settings and there are already other applications runni
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.
--
Vie
On Tue, Jul 29, 2014 at 6:33 AM, DuyHai Doan wrote:
> No, I meant why don't you set the partitioner of 2.0.8 cluster to
> RandomPartitioner instead of Mumur3 ?
>
+1
Murmur3 is a semi-marginal win, OP probably does not need it on this
particular cluster.
=Rob
nd do not
>>> necessarily represent those of Genetwister. Finally, the recipient should
>>> check this e-mail and any attachments for the presence of viruses.
>>> Genetwister accepts no liability for any damage caused by any virus
>>> transmitted by this e-mai
tted by this e-mail or damage caused by the use of the information
>> contained in this e-mail.
>>
>> From: tsi [thorsten.s...@t-systems.com]
>> Sent: Tuesday, July 29, 2014 2:53 PM
>> To: cassandra-u...@incubator.apache.org
>&
thorsten.s...@t-systems.com]
> Sent: Tuesday, July 29, 2014 2:53 PM
> To: cassandra-u...@incubator.apache.org
> Subject: Re: Migration from Cassandra 1.2.5 to Cassandra 2.0.8 with
> changed partitioner settings
>
> We are moving our application to a plattform with this partitioner s
[thorsten.s...@t-systems.com]
Sent: Tuesday, July 29, 2014 2:53 PM
To: cassandra-u...@incubator.apache.org
Subject: Re: Migration from Cassandra 1.2.5 to Cassandra 2.0.8 with changed
partitioner settings
We are moving our application to a plattform with this partitioner setting
and as far as I know
No, I meant why don't you set the partitioner of 2.0.8 cluster to
RandomPartitioner instead of Mumur3 ?
On Tue, Jul 29, 2014 at 2:53 PM, tsi wrote:
> We are moving our application to a plattform with this partitioner setting
> and as far as I know there is no way to specify a partitioner on key
We are moving our application to a plattform with this partitioner setting
and as far as I know there is no way to specify a partitioner on keyspace
level.
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Migration-from-Cassandra-1-2-5-to-Cassand
Why don't you stay with random partitioner ?
On Tue, Jul 29, 2014 at 2:30 PM, tsi wrote:
> We are planning to migrate data from a Cassandra 1.2.5 to a new Cassandra
> 2.0.8 cluster with changed partitioner settings (1.2.5:
> org.apache.cassandra.dht.RandomPartitioner, 2.0.8:
> org.apache.cassa
We are planning to migrate data from a Cassandra 1.2.5 to a new Cassandra
2.0.8 cluster with changed partitioner settings (1.2.5:
org.apache.cassandra.dht.RandomPartitioner, 2.0.8:
org.apache.cassandra.dht.Murmur3Partitioner). Restoring a snapshot via
BulkLoader fails with error message
SSTableRe
13 matches
Mail list logo
