If you have a test environment which has identical or almost identical to
your production, doing upgrade in test environment would give more
confidence. If it is *production*, I would not even want to keep my finger
cross or hope in anyway it would work for this major upgrade 1.0.x to 2.0.x
. A saf
On Mon, Jan 20, 2014 at 1:47 AM, Or Sher wrote:
> Can I use sstableloader to load SSTables from a RandomPartitioner cluster
> to a Murmuer3Partitioner cluster?
>
My expectation would be yes, if you try it and it works, let us know!
=Rob
Thanks.
Can I use sstableloader to load SSTables from a RandomPartitioner cluster
to a Murmuer3Partitioner cluster?
On Thu, Jan 16, 2014 at 9:24 PM, Arya Goudarzi wrote:
> Read the upgrade best practices
>
> http://www.datastax.com/docs/1.1/install/upgrading#best-practices
>
> You cannot cha
Read the upgrade best practices
http://www.datastax.com/docs/1.1/install/upgrading#best-practices
You cannot change partitioner
http://www.datastax.com/documentation/cassandra/1.2/webhelp/cassandra/architecture/architecturePartitionerAbout_c.html
On Thu, Jan 16, 2014 at 2:04 AM, Or Sher wrote
Hi,
In order to upgrade our env from 1.0.9 to 2.0 I thought about the following
steps:
- Creating a new 1.0.9 cluster
- Creating the keyspaces and column families
(I need to move one keyspace data to the new cluster and so:)
- Moving all xKS SSTables from old cluster to every node in the new clus
