?
tsi wrote
> OK, now supposing Cassandra is run in a VM that crashes and I restore it
> from a snapshot done some time ago. Data is stored redundantly
> (replication factor 3) and I'm using consistency level QUORUM for reads
> and writes. That means no data should be lost as the la
OK, now supposing Cassandra is run in a VM that crashes and I restore it from
a snapshot done some time ago. Data is stored redundantly (replication
factor 3) and I'm using consistency level QUORUM for reads and writes. That
means no data should be lost as the latest data will at least be stored on
In the datastax documentation there is a description how to replace a dead
node
(http://www.datastax.com/documentation/cassandra/2.0/cassandra/operations/ops_replace_node_t.html).
Is the replace_address option required even if the IP address of the new
node is the same as the original one (I read
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
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
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
