Sorry, my bad. I misread as 1.2.4 for some reason! You should be able to do it with the 2-way upgrade then. Don't forget that once you upgrade to 2.0.x you need to perform a "nodetool upgradesstables" and this is where, in my point of view, things can get tricky. First make sure you have the space available (it will probably duplicate your space, since both new and old tables need to coexist for a while. It depends if the process goes in parallel or not, which I don't know). And some for security sake I would do it one by one, so if things go bad, you have one node down. Once this process is done, the upgrade to 2.1.x should be simple. Make sure the new machines joining in are 2.0.X. Then upgrade all the cluster. Maybe you can even work it from your version to 2.1.x since you are already network compatible, but 2.1.x brings new features (the new counters) that could prove problematic if (I assume that is the case) you will keep your cluster running.
Some oversimplified documentation can also be found here: http://www.datastax.com/documentation/upgrade/doc/upgrade/cassandra/upgradeCassandraDetails.html I had my fair share of bad upgrades with Cassandra, and also a couple of good ones. The approach I used last time was the safest I ever did, but for sure, the most time consuming of them all. Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: cjrolo | Linkedin: *linkedin.com/in/carlosjuzarterolo <http://linkedin.com/in/carlosjuzarterolo>* Tel: 1649 www.pythian.com On Thu, Jan 29, 2015 at 4:52 PM, Sibbald, Charles <charles.sibb...@bskyb.com > wrote: > Hi Carlos, > > We are running 1.2.14 which is higher than 1.2.9 so I have an assumption > that the network layer is compatible, or do you specifically mean that 2.10 > is not compatible with 1.2.x ? > > Regards > > Charles > > > From: Carlos Rolo <r...@pythian.com> > Reply-To: "user@cassandra.apache.org" <user@cassandra.apache.org> > Date: Thursday, 29 January 2015 14:47 > To: "user@cassandra.apache.org" <user@cassandra.apache.org> > Subject: Re: Upgrading from Cassandra 1.2.14 to Cassandra 2.10 > > Hello Charles, > > I think you have to do a 2-time upgrade given SSTables and Network > incompatibilities between versions. You have to upgrade to 2.0 and then to > 2.1. > > Acording to this > http://www.datastax.com/documentation/upgrade/doc/upgrade/cassandra/upgradeC_c.html > you should even do a upgrade to 1.2.9 first. > > The major upgrade I did 1.2.x to 2.0.x I did it putting a new ring with > the 2.0 machines, clients writing to both and the move the old machines > from one ring to the other like they were brand new machines. The > historical data was imported in batches. > > > > Regards, > > Carlos Juzarte Rolo > Cassandra Consultant > > Pythian - Love your data > > rolo@pythian | Twitter: cjrolo | Linkedin: *linkedin.com/in/carlosjuzarterolo > <http://linkedin.com/in/carlosjuzarterolo>* > Tel: 1649 > www.pythian.com > > On Thu, Jan 29, 2015 at 3:15 PM, Sibbald, Charles < > charles.sibb...@bskyb.com> wrote: > >> Hi All, >> >> I am looking into the possibility of upgrading from Cassandra 1.2.14 to >> Cassandra 2.1 in the following manor. >> >> I have a large Cassandra cluster with dozens of nodes, and would like >> to build new instances at version 2.1 to join the cluster and once they >> have successfully joined the rink these should then stream data in. >> >> Once they have fully joined the cluster I would like to decommission a >> single Cassandra 1.2.14 instance, and repeat. >> >> Due to the fact that our 2.1 installations have a different directory >> layout we would like to go with this ‘streaming’ option for the upgrade >> rather than an inplace upgrade. >> >> Does anyone foresee any issues with this. >> >> Thanks in advance. >> >> Regards >> >> Charles >> Information in this email including any attachments may be privileged, >> confidential and is intended exclusively for the addressee. The views >> expressed may not be official policy, but the personal views of the >> originator. If you have received it in error, please notify the sender by >> return e-mail and delete it from your system. You should not reproduce, >> distribute, store, retransmit, use or disclose its contents to anyone. >> Please note we reserve the right to monitor all e-mail communication >> through our internal and external networks. SKY and the SKY marks are >> trademarks of British Sky Broadcasting Group plc and Sky International AG >> and are used under licence. British Sky Broadcasting Limited (Registration >> No. 2906991), Sky-In-Home Service Limited (Registration No. 2067075) and >> Sky Subscribers Services Limited (Registration No. 2340150) are direct or >> indirect subsidiaries of British Sky Broadcasting Group plc (Registration >> No. 2247735). All of the companies mentioned in this paragraph are >> incorporated in England and Wales and share the same registered office at >> Grant Way, Isleworth, Middlesex TW7 5QD. >> > > > -- > > > > Information in this email including any attachments may be privileged, > confidential and is intended exclusively for the addressee. The views > expressed may not be official policy, but the personal views of the > originator. If you have received it in error, please notify the sender by > return e-mail and delete it from your system. You should not reproduce, > distribute, store, retransmit, use or disclose its contents to anyone. > Please note we reserve the right to monitor all e-mail communication > through our internal and external networks. SKY and the SKY marks are > trademarks of British Sky Broadcasting Group plc and Sky International AG > and are used under licence. British Sky Broadcasting Limited (Registration > No. 2906991), Sky-In-Home Service Limited (Registration No. 2067075) and > Sky Subscribers Services Limited (Registration No. 2340150) are direct or > indirect subsidiaries of British Sky Broadcasting Group plc (Registration > No. 2247735). All of the companies mentioned in this paragraph are > incorporated in England and Wales and share the same registered office at > Grant Way, Isleworth, Middlesex TW7 5QD. > -- --
