+1 what Jon said On 18 Oct. 2017 06:38, "Jon Haddad" <j...@jonhaddad.com> wrote:
> I recommend going all the way to 2.2. > > On Oct 17, 2017, at 12:37 PM, Jeff Jirsa <jji...@gmail.com> wrote: > > You’ll go from 1.2 to 2.0 to 2.1 - should be basic steps: > - make sure you have all 1.2 sstables by running upgradesstable > - one node at a time, swap the 1.2 binaries for latest in 2.0 > - once all nodes are 2.0, run upgradesstables on each node (one at a time) > - one node at a, swap the 2.0 binaries for latest 2.1 > - once all are 2.1, upgradesstables again > > You’ll want to read NEWS.txt for the versions as you upgrade in case there > are any changes to config yaml or intermediate steps - > https://github.com/apache/cassandra/blob/cassandra-1.2/NEWS.txt for 1.2 > > Not a bad idea to find a consultant that does this often because they may > know of some rough edges in the process - this isn’t an endorsement, but I > imagine the folks at Pythian do this a lot, and Instaclustr / TheLastPickle > both have teams of consultants to help you along as well. > > > > On Oct 17, 2017, at 11:20 AM, David Ellis <da...@ellisonline.ca> wrote: > > I have a large Cassandra 1.2.9 based enterprise application with a > considerable amount of data. > > I’d like to begin the process of upgrading my existing java application > and the database to Cassandra 2.1. > > Anyone have some suggestions where to begin? Any experts looking for some > consulting income :) > > David > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org > For additional commands, e-mail: user-h...@cassandra.apache.org > > >
