You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Tobias Hauth <to...@gmail.com> on 2015/02/20 18:25:08 UTC

Moving from 2.1.x to 2.0.x

Hi,

Is there an recommended way of moving data from a 2.1.x cluster to a 2.0.x
cluster? We would like to downgrade to a more stable version of C* and just
adding nodes with C* 2.0.12 results in schema miss-matches and 'nodetool
describecluster' reports different schema versions.

Thanks,
Tobias

Re: Moving from 2.1.x to 2.0.x

Posted by Tobias Hauth <to...@gmail.com>.
Thanks,
Tobias

On Fri, Feb 20, 2015 at 11:28 AM, Robert Coli <rc...@eventbrite.com> wrote:

> On Fri, Feb 20, 2015 at 9:25 AM, Tobias Hauth <to...@gmail.com>
> wrote:
>
>> Is there an recommended way of moving data from a 2.1.x cluster to a
>> 2.0.x cluster? We would like to downgrade to a more stable version of C*
>> and just adding nodes with C* 2.0.12 results in schema miss-matches and
>> 'nodetool describecluster' reports different schema versions.
>>
>
> For the record, the activity you are doing is unsupported in any way.
> Downgrades of any kind are not supported in Cassandra.
>
> However from reading NEWS.txt, the sstable format is the same. So as long
> as you don't try to copy the system keyspace along (which is likely
> significantly changed) you "should" be able to create the schema and be
> fine?
>
> I would use whichever approach here is more appropriate :
>
> http://www.pythian.com/blog/bulk-loading-options-for-cassandra/
>
> =Rob
>
>

Re: Moving from 2.1.x to 2.0.x

Posted by Robert Coli <rc...@eventbrite.com>.
On Fri, Feb 20, 2015 at 9:25 AM, Tobias Hauth <to...@gmail.com>
wrote:

> Is there an recommended way of moving data from a 2.1.x cluster to a 2.0.x
> cluster? We would like to downgrade to a more stable version of C* and just
> adding nodes with C* 2.0.12 results in schema miss-matches and 'nodetool
> describecluster' reports different schema versions.
>

For the record, the activity you are doing is unsupported in any way.
Downgrades of any kind are not supported in Cassandra.

However from reading NEWS.txt, the sstable format is the same. So as long
as you don't try to copy the system keyspace along (which is likely
significantly changed) you "should" be able to create the schema and be
fine?

I would use whichever approach here is more appropriate :

http://www.pythian.com/blog/bulk-loading-options-for-cassandra/

=Rob