different versions in upgrade
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 riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Re: different versions in upgrade
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 lpper...@gmail.com 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 riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Re: different versions in upgrade
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 jeremiah.pesc...@gmail.com 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 lpper...@gmail.com 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 riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Re: different versions in upgrade
Same here, except that Riak 1.3.2 did that for me automatically. As Jeremiah mentioned, you should go first to 1.3.2 on all nodes, per node the first time Riak starts it will take some time upgrading the 2i indexes storage format, if you see any weirdness then execute riak-admin reformat-indexes as soon as you upgrade a node, 1 by 1. Before you even start read the release notes for each major version besides the rolling upgrade doc: *Riak 1.3.2:* https://github.com/basho/riak/blob/1.3/RELEASE-NOTES.md *Riak 1.4.1:* https://github.com/basho/riak/blob/1.4/RELEASE-NOTES.md HTH, Guido. On 13/08/13 13:41, Bhuwan Chawla wrote: 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 jeremiah.pesc...@gmail.com mailto:jeremiah.pesc...@gmail.com 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 lpper...@gmail.com mailto:lpper...@gmail.com 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 riak-users@lists.basho.com mailto:riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com ___ riak-users mailing list riak-users@lists.basho.com mailto:riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Re: different versions in upgrade
Also, in theory if you have at least 5 nodes in the cluster one node down at a time doesn't stop your cluster from working properly. You could do the following node by node which I have done several times: 1. Stop Riak on the upgrading node and in another node mark the upgrading node as down (riak-admin down riak@upgrading-node) 2. Upgrade Riak on that node to version 1.3.2, start it up and wait till it is completely operative (riak_kv is up and all transfers are finished, check by typing riak-admin transfers) 3. For Riak 1.3.2 once the step is over, type riak-admin reformat-indexes and tail -f /var/log/riak/console.log which should be done really fast if there isn't anything to fix. 4. Do 1 to 3 per node. 5. Do 1 and 2 but for for Riak 1.4.1. HTH, Guido. On 13/08/13 13:50, Guido Medina wrote: Same here, except that Riak 1.3.2 did that for me automatically. As Jeremiah mentioned, you should go first to 1.3.2 on all nodes, per node the first time Riak starts it will take some time upgrading the 2i indexes storage format, if you see any weirdness then execute riak-admin reformat-indexes as soon as you upgrade a node, 1 by 1. Before you even start read the release notes for each major version besides the rolling upgrade doc: *Riak 1.3.2:* https://github.com/basho/riak/blob/1.3/RELEASE-NOTES.md *Riak 1.4.1:* https://github.com/basho/riak/blob/1.4/RELEASE-NOTES.md HTH, Guido. On 13/08/13 13:41, Bhuwan Chawla wrote: 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 jeremiah.pesc...@gmail.com mailto:jeremiah.pesc...@gmail.com 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 lpper...@gmail.com mailto:lpper...@gmail.com 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 riak-users@lists.basho.com mailto:riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com ___ riak-users mailing list riak-users@lists.basho.com mailto:riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Re: different versions in upgrade
Louis-Philippe et al: You can follow the rolling upgrade procedure to upgrade a node from 1.2 to 1.4.x directly. The note in the instructions only concerns upgrading from 1.0 to 1.4. No need to stop at 1.3.2. Thanks, Charlie Voiselle On Aug 13, 2013, at 9:23 AM, Guido Medina guido.med...@temetra.com wrote: Also, in theory if you have at least 5 nodes in the cluster one node down at a time doesn't stop your cluster from working properly. You could do the following node by node which I have done several times: Stop Riak on the upgrading node and in another node mark the upgrading node as down (riak-admin down riak@upgrading-node) Upgrade Riak on that node to version 1.3.2, start it up and wait till it is completely operative (riak_kv is up and all transfers are finished, check by typing riak-admin transfers) For Riak 1.3.2 once the step is over, type riak-admin reformat-indexes and tail -f /var/log/riak/console.log which should be done really fast if there isn't anything to fix. Do 1 to 3 per node. Do 1 and 2 but for for Riak 1.4.1. HTH, Guido. On 13/08/13 13:50, Guido Medina wrote: Same here, except that Riak 1.3.2 did that for me automatically. As Jeremiah mentioned, you should go first to 1.3.2 on all nodes, per node the first time Riak starts it will take some time upgrading the 2i indexes storage format, if you see any weirdness then execute riak-admin reformat-indexes as soon as you upgrade a node, 1 by 1. Before you even start read the release notes for each major version besides the rolling upgrade doc: Riak 1.3.2: https://github.com/basho/riak/blob/1.3/RELEASE-NOTES.md Riak 1.4.1: https://github.com/basho/riak/blob/1.4/RELEASE-NOTES.md HTH, Guido. On 13/08/13 13:41, Bhuwan Chawla wrote: 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 jeremiah.pesc...@gmail.com 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 lpper...@gmail.com 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 riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
