It may be more valuable to set up your test cluster as the same version,
and make sure your tokens are the same.  then copy over your sstables.
 you'll have an exact replica of prod & you can test your upgrade process.

On Fri Dec 19 2014 at 11:04:58 AM Ryan Svihla <rsvi...@datastax.com> wrote:

> In theory, you could always do a data dump ..sstable to json and back for
> example, but you'd have to have your schema setup ,and I've not actually
> done this myself so YMMV.
>
> I've helped a bunch of folks with that upgrade path and while it's time
> consuming it does work.
>
> On Fri, Dec 19, 2014 at 8:49 AM, Langston, Jim <jim.langs...@dynatrace.com
> > wrote:
>>
>>  Thanks, this looks uglier , I double checked my production cluster ( I
>> have a staging and development cluster as well ) and
>> production is on 1.2.8. A copy of the data resulted in a mssage :
>>
>>  Exception encountered during startup: Incompatible SSTable found.
>> Current version ka is unable to read file:
>> /cassandra/apache-cassandra-2.1.2/bin/../data/data/system/schema_keyspaces/system-schema_keyspaces-ic-150.
>> Please run upgradesstables.
>>
>>  Is the move going to to be 1.2.8 --> 1.2.9 --> 2.0.x --> 2.1.2 ??
>>
>>  Can I just dump the data and import it into 2.1.2 ??
>>
>>
>>  Jim
>>
>>   From: Ryan Svihla <rsvi...@datastax.com>
>> Reply-To: <user@cassandra.apache.org>
>> Date: Thu, 18 Dec 2014 06:00:09 -0600
>> To: <user@cassandra.apache.org>
>> Subject: Re: simple data movement ?
>>
>>  I'm not sure that'll work with that many version moves in the middle,
>> upgrades are to my knowledge only tested between specific steps, namely
>> from 1.2.9 to the latest 2.0.x
>>
>>
>> http://www.datastax.com/documentation/upgrade/doc/upgrade/cassandra/upgradeC_c.html
>>  Specifically:
>>
>>   Cassandra 2.0.x restrictions¶
>> <http://www.datastax.com/documentation/upgrade/doc/upgrade/cassandra/upgradeC_c.html?scroll=concept_ds_yqj_5xr_ck__section_ubt_nwr_54>
>>
>> After downloading DataStax Community
>> <http://planetcassandra.org/cassandra/>, upgrade to Cassandra directly
>> from Cassandra 1.2.9 or later. Cassandra 2.0 is not network- or
>> SSTable-compatible with versions older than 1.2.9. If your version of
>> Cassandra is earlier than 1.2.9 and you want to perform a rolling restart
>> <http://www.datastax.com/documentation/cassandra/1.2/cassandra/glossary/gloss_rolling_restart.html>,
>> first upgrade the entire cluster to 1.2.9, and then to Cassandra 2.0.
>>  Cassandra 2.1.x restrictions¶
>> <http://www.datastax.com/documentation/upgrade/doc/upgrade/cassandra/upgradeC_c.html?scroll=concept_ds_yqj_5xr_ck__section_qzx_pwr_54>
>>
>> Upgrade to Cassandra 2.1 from Cassandra 2.0.7 or later.
>>
>> Cassandra 2.1 is not compatible with Cassandra 1.x SSTables. First
>> upgrade the nodes to Cassandra 2.0.7 or later, start the cluster, upgrade
>> the SSTables, stop the cluster, and then upgrade to Cassandra 2.1.
>>
>> On Wed, Dec 17, 2014 at 10:55 PM, Ben Bromhead <b...@instaclustr.com>
>> wrote:
>>>
>>> Just copy the data directory from each prod node to your test node (and
>>> relevant configuration files etc).
>>>
>>>  If your IP addresses are different between test and prod, follow
>>> https://engineering.eventbrite.com/changing-the-ip-address-of-a-cassandra-node-with-auto_bootstrapfalse/
>>>
>>>
>>> On 18 December 2014 at 09:10, Langston, Jim <jim.langs...@dynatrace.com>
>>> wrote:
>>>>
>>>>  Hi all,
>>>>
>>>>  I have set up a test environment with C* 2.1.2, wanting to test our
>>>> applications against it. I currently have C* 1.2.9 in production and
>>>> want
>>>> to use that data for testing. What would be a good approach for simply
>>>> taking a copy of the production data and moving it into the test env and
>>>> having the test env C* use that data ?
>>>>
>>>>  The test env. is identical is size, with the difference being the
>>>> versions
>>>> of C*.
>>>>
>>>>  Thanks,
>>>>
>>>>  Jim
>>>>  The contents of this e-mail are intended for the named addressee only.
>>>> It contains information that may be confidential. Unless you are the named
>>>> addressee or an authorized designee, you may not copy or use it, or
>>>> disclose it to anyone else. If you received it in error please notify us
>>>> immediately and then destroy it
>>>>
>>>
>>>
>>>   --
>>>
>>> Ben Bromhead
>>>
>>> Instaclustr | www.instaclustr.com | @instaclustr
>>> <http://twitter.com/instaclustr> | +61 415 936 359
>>>
>>
>>
>>  --
>>
>> [image: datastax_logo.png] <http://www.datastax.com/>
>>
>> Ryan Svihla
>>
>> Solution Architect
>>
>> [image: twitter.png] <https://twitter.com/foundev> [image: linkedin.png]
>> <http://www.linkedin.com/pub/ryan-svihla/12/621/727/>
>>
>>  DataStax is the fastest, most scalable distributed database technology,
>> delivering Apache Cassandra to the world’s most innovative enterprises.
>> Datastax is built to be agile, always-on, and predictably scalable to any
>> size. With more than 500 customers in 45 countries, DataStax is the
>> database technology and transactional backbone of choice for the worlds
>> most innovative companies such as Netflix, Adobe, Intuit, and eBay.
>>
>>     The contents of this e-mail are intended for the named addressee
>> only. It contains information that may be confidential. Unless you are the
>> named addressee or an authorized designee, you may not copy or use it, or
>> disclose it to anyone else. If you received it in error please notify us
>> immediately and then destroy it
>>
>
>
> --
>
> [image: datastax_logo.png] <http://www.datastax.com/>
>
> Ryan Svihla
>
> Solution Architect
>
> [image: twitter.png] <https://twitter.com/foundev> [image: linkedin.png]
> <http://www.linkedin.com/pub/ryan-svihla/12/621/727/>
>
> DataStax is the fastest, most scalable distributed database technology,
> delivering Apache Cassandra to the world’s most innovative enterprises.
> Datastax is built to be agile, always-on, and predictably scalable to any
> size. With more than 500 customers in 45 countries, DataStax is the
> database technology and transactional backbone of choice for the worlds
> most innovative companies such as Netflix, Adobe, Intuit, and eBay.
>
>

Reply via email to