Thanks Ben and Brooke! @Brooke, I'd like to do that because I want to install Centos 7 on those machines instead of the current Centos 6. To achieve that, I need to make a new installation of the OS, meaning taking the server down. So if that's the case, and I can't perform the upgrade online, why not install everything anew? By the way, if I do take the longer way and add a new 2.2.8 node to the cluster, do I still need to perform upgradesstables on the new node?
Shalom Sagges DBA T: +972-74-700-4035 <http://www.linkedin.com/company/164748> <http://twitter.com/liveperson> <http://www.facebook.com/LivePersonInc> We Create Meaningful Connections <https://engage.liveperson.com/idc-mobile-first-consumer/?utm_medium=email&utm_source=mkto&utm_campaign=idcsig> On Tue, Nov 29, 2016 at 12:38 PM, Brooke Jensen <bro...@instaclustr.com> wrote: > Hi Shalom. > > That seems like the long way around doing it. If you clear the data from > the node then add it back in then you will have to restream and recompact > the data again for each node. Is there a particular reason why you would > need to do it this way? > > The way we do it is to update Cassandra on each node as per the steps Ben > linked to. Once all nodes are on the newer version you can run > upgradesstables. If you have a large cluster and are using racks you can do > the upgrade one rack at a time to speed things up. Either way, this should > enable you to do the upgrade fairly quickly with no downtime. > > Regards, > *Brooke Jensen* > VP Technical Operations & Customer Services > www.instaclustr.com | support.instaclustr.com > <https://support.instaclustr.com/hc/en-us> > > This email has been sent on behalf of Instaclustr Limited (Australia) and > Instaclustr Inc (USA). This email and any attachments may contain > confidential and legally privileged information. If you are not the > intended recipient, do not copy or disclose its content, but please reply > to this email immediately and highlight the error to the sender and then > immediately delete the message. > > On 29 November 2016 at 21:12, Ben Dalling <b.dall...@locp.co.uk> wrote: > >> Hi Shalom, >> >> There is a pretty good write up of the procedure written up here ( >> https://docs.datastax.com/en/upgrade/doc/upgrade/cassandra/ >> upgrdCassandraDetails.html). Things to highlight are: >> >> >> - Don't have a repair running while carrying out the upgrade (so that >> does timebox your upgrade). >> - When the upgrade is complete. Run "nodetool upgradesstables" on >> all the nodes. >> >> >> Pretty much what you suggested. >> >> Best wishes, >> >> Ben >> >> On 29 November 2016 at 09:52, Shalom Sagges <shal...@liveperson.com> >> wrote: >> >>> Hi Everyone, >>> >>> Hypothetically speaking, can I add a new node with version 2.2.8 to a >>> 2.0.14 cluster? >>> Meaning, instead of upgrading the cluster, I'd like to remove a node, >>> clear all its data, install 2.2.8 and add it back to the cluster, with the >>> process eventually performed on all nodes one by one. >>> >>> Is this possible? >>> >>> Thanks! >>> >>> >>> Shalom Sagges >>> DBA >>> T: +972-74-700-4035 >>> <http://www.linkedin.com/company/164748> <http://twitter.com/liveperson> >>> <http://www.facebook.com/LivePersonInc> We Create Meaningful Connections >>> >>> <https://engage.liveperson.com/idc-mobile-first-consumer/?utm_medium=email&utm_source=mkto&utm_campaign=idcsig> >>> >>> >>> This message may contain confidential and/or privileged information. >>> If you are not the addressee or authorized to receive this on behalf of >>> the addressee you must not use, copy, disclose or take action based on this >>> message or any information herein. >>> If you have received this message in error, please advise the sender >>> immediately by reply email and delete this message. Thank you. >>> >> >> >> >> -- >> *Ben Dalling** MSc, CEng, MBCS CITP* >> League of Crafty Programmers Ltd >> Mobile: +44 (0) 776 981-1900 >> email: b.dall...@locp.co.uk >> www: http://www.locp.co.uk >> http://www.linkedin.com/in/bendalling >> > > -- This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this on behalf of the addressee you must not use, copy, disclose or take action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply email and delete this message. Thank you.
