Hi Jonathon,
I created the schema manually. I took the schema definition from the old
cluster using "desc {keyspace_name}" and then ran those cql statements in
the new cluster. I didn't do anything with the system keyspaces.
Cheers,
Ajaya
On Sat, Jan 30, 2016 at 11:29 PM, Jonathan Haddad <j...@jonhaddad.com> wrote:
> Did you also copy the system keyspaces or did you create the schema
> manually?
>
> On Sat, Jan 30, 2016 at 9:39 AM Jeff Jirsa <jeff.ji...@crowdstrike.com>
> wrote:
>
>> Upgrade from 2.1.9+ directly to 3.0 is supported:
>>
>> https://github.com/apache/cassandra/blob/cassandra-3.0/NEWS.txt#L83-L85
>>
>> - Upgrade to 3.0 is supported from Cassandra 2.1 versions greater or
>> equal to 2.1.9, or Cassandra 2.2 versions greater or equal to 2.2.2.
>> Upgrade from Cassandra 2.0 and older versions is not supported.
>>
>>
>> From: DuyHai Doan
>> Reply-To: "user@cassandra.apache.org"
>> Date: Saturday, January 30, 2016 at 3:54 AM
>> To: "user@cassandra.apache.org"
>> Subject: Re: Problem while migrating a single node cluster from 2.1 to
>> 3.2
>>
>> You need to upgrade first to C* 2.2 before migrating to C* 3.x
>>
>> For each version, read the NEWS.txt file and follow the procedure:
>>
>> From 2.1.x to 2.2.x :
>> https://github.com/apache/cassandra/blob/cassandra-2.2/NEWS.txt
>>
>> From 2.2.x to 3.x:
>> https://github.com/apache/cassandra/blob/cassandra-3.0/NEWS.txt
>>
>> On Sat, Jan 30, 2016 at 8:10 AM, Ajaya Agrawal <ajku....@gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I am a newbie when it comes to Cassandra administration and operation.
>>> We have a single node cluster running 2.1 in EC2 and we are planning to
>>> move it to better single machine instance and want to run 3.2 on that.
>>>
>>> I installed 3.2 on the new machine and created a snapshot of the old
>>> cluster and then copied over all the relevant directories to the new
>>> machine in the appropriate directory. Specifically I copied
>>> "/var/lib/cassandra/data/{keyspace} from old machine to the new machine.
>>> Before that I created relevant schema in the new cluster. I was hoping that
>>> Cassandra would see new directories and load up the new copied SSTables
>>> automatically. At the least I was hoping to see the snapshot created in the
>>> old cluster, when I did a "nodetool listsnapshots" in the new cluster.
>>>
>>> I have also changed the name of the new cluster.
>>>
>>> Please help me and let me know if I forgot to add any detail.
>>>
>>> Cheers,
>>> Ajaya
>>>
>>
>>
