Re: Rolling upgrade from 1.4.2 to 2.0.5

Thanks Dmitri. I’ll try it with the modified reip script! ​ On Wed, Aug 26, 2015 at 10:39 PM, Dmitri Zagidulin wrote: > Hi Sujay, > > Checking into it, it seems like there is a bug with 'reip' in 1.4.2. > > You have a couple of options, then. > > 1) Since you're just trying to verify the data,

Re: Rolling upgrade from 1.4.2 to 2.0.5

Hi Sujay, Checking into it, it seems like there is a bug with 'reip' in 1.4.2. You have a couple of options, then. 1) Since you're just trying to verify the data, you can actually restore all the files except for the 'ring' directory. And then just form a new cluster of 5 nodes, with different I

Re: Rolling upgrade from 1.4.2 to 2.0.5

Thanks for your reply Dmitri. ubuntu@test-riak-products-hetzner-04:~$ sudo riak ping Node 'riak@172.16.16.211' not responding to pings. ubuntu@test-riak-products-hetzner-04:~$ ps -ef | grep erl ubuntu 13786 13709 0 07:12 pts/000:00:00 grep --color=auto erl ubuntu@test-riak-products-hetzner-

Re: Rolling upgrade from 1.4.2 to 2.0.5

Can you paste me the command-line output of 'riak-admin reip', and the error message? As far as I know, 'reip' requires the node to be not running. (This was the case at least as far back as Riak 1.3, and probably earlier). I don't think there are ways of verifying the backup while the nodes are n

Re: Rolling upgrade from 1.4.2 to 2.0.5

Thanks Dmitri. I tried that, but with no luck. I replaced the ring and bitcask data directories. But I can’t run riak-admin reip ... because it complains that riak isn’t running. However, I can’t start riak (I get the following in /var/log/riak/error.log ). (The existing cluster is the 192.168.3

Re: Rolling upgrade from 1.4.2 to 2.0.5

Hi Sujay, This is where we get into the fact that maintaining docs across many versions is a hard problem :) You'll want to follow the instructions laid out in http://docs.basho.com/riak/latest/ops/running/nodes/renaming/#Clusters-from-Backups (the Clusters from Backup section, specifically). Tha

Re: Rolling upgrade from 1.4.2 to 2.0.5

Hi guys I am looking at the instructions here: http://docs.basho.com/riak/1.4.2/ops/running/nodes/renaming/ However, these are instructions for renaming an existing cluster ‘in-place’. What I have is an existing 5 node cluster. I have brought up a completely new (and separate) 5 node cluster. I

Re: Rolling upgrade from 1.4.2 to 2.0.5

Hi Sujay, Yes, riak.conf is a riak 2 thing. If you're running 1.4, you would change the -setcookie in vm.args, exactly. And no, the node name doesn't have to match the cookie. The two are independent. On Tue, Aug 11, 2015 at 3:22 PM, Sujay Mansingh wrote: > Oh and also, does the first part of

Re: Rolling upgrade from 1.4.2 to 2.0.5

Oh and also, does the first part of the riak node name have to match the cookie? I.e. If I change the cookie to riaktest, does the node name have to be riaktest@{{ ip_addr }} ? On Tuesday, August 11, 2015, Sujay Mansingh wrote: > Thanks Dmitri > > When you say the cookie must be modified in /etc

Re: Rolling upgrade from 1.4.2 to 2.0.5

Thanks Dmitri When you say the cookie must be modified in /etc/riak/riak.conf, is that a riak 2 thing? I can see a -setcookie riak line in /etc/riak/vm.args, is that what you mean? Sujay ​ On Thu, Aug 6, 2015 at 2:11 PM, Dmitri Zagidulin wrote: > Sujay, > > You're right - the best way to verif

Re: Rolling upgrade from 1.4.2 to 2.0.5

Sujay, You're right - the best way to verify the backup is to bring up a separate 5 node cluster, and restore it from the backup files. The procedure is slightly more involved than untar-ing, though. The backed up ring directories from the original cluster will contain the node ids (which rely on

Re: Rolling upgrade from 1.4.2 to 2.0.5

Thanks Magnus & John. Yes certainly I will test it on a separate cluster first! Which is related to another question I have. If I want to backup I can archive the directories on the nodes as described here: http://docs.basho.com/riak/latest/ops/running/backups/#OS-Specific-Directory-Locations Bu

Re: Rolling upgrade from 1.4.2 to 2.0.5

On 5 August 2015 at 18:53, John Daily wrote: > That’s correct: upgrades to either 2.0.x or 2.1.x are supported from the > 1.4 series. > > Side note: I definitely recommend testing the upgrade process in a QA > environment first. > > -John > Hi Sujay, The latest release in the 2.0 series is 2.0.

Re: Rolling upgrade from 1.4.2 to 2.0.5

That’s correct: upgrades to either 2.0.x or 2.1.x are supported from the 1.4 series. Side note: I definitely recommend testing the upgrade process in a QA environment first. -John On Aug 5, 2015, at 12:13 PM, Sujay Mansingh wrote: Hello all, I have a 5 node riak cluster, all nodes running 1.4