Having done a similar upgrade, a gotcha to keep in mind:
"Note for Secondary Index users If you use Riak's Secondary Indexes and are upgrading from a version prior to Riak version 1.3.1, you need to reformat the indexes using the riak-admin reformat-indexes command" On Tue, Aug 13, 2013 at 8:36 AM, Jeremiah Peschka < [email protected]> wrote: > From http://docs.basho.com/riak/latest/ops/running/rolling-upgrades/ it > looks like you should upgrade to 1.3.2 and then 1.4.1 > > Depending on how badly you need the extra capacity, it would probably be > better to start by upgrading all nodes and then adding the new one. > > -- > Jeremiah Peschka - Founder, Brent Ozar Unlimited > MCITP: SQL Server 2008, MVP > Cloudera Certified Developer for Apache Hadoop > > On Aug 13, 2013, at 5:06 AM, Louis-Philippe Perron <[email protected]> > wrote: > > Hi riak peoples, > I'm in the process of adding a new node to a aging (1 node) cluster. I > would like to know what would be the prefered incrementing upgrade to get > all my nodes on the latest riak version. The best scenario would also have > the least downtime. The old node is at riak version 1.2.1. > > My actual plan is: > > - install riak 1.4.1 on the new node > - add the new 1.4.1 node to the old 1.2.1 cluster. > - bring the 1.2.1 node offline > - upgrade the 1.2.1 node to 1.4.1 > - put the upgraded node back online > > will this work? > thanks! > > > _______________________________________________ > riak-users mailing list > [email protected] > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > > > _______________________________________________ > riak-users mailing list > [email protected] > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > >
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
