Re: Upgrade procedure from 0.12 to 0.13

2010-10-13 Thread Mojito Sorbet
To me, inability to upgrade a large Riak cluster incrementally would be a major factor against choosing it. The evolution of the protocols must be constrained so that this is possible. Now is the time to work that out, while the version number still starts with "0". On Wed, 2010-10-13 at 11:34

Re: Upgrade procedure from 0.12 to 0.13

2010-10-13 Thread David Smith
To the best of my knowledge, there are no changes between 0.12->0.13 that would prevent a rolling upgrade. That said, we have not tested that specific use-case yet -- it's in the pipeline to be part of our pre-release automated testing. I'd recommend you'd try it on a QA cluster before doing it li

Re: Upgrade procedure from 0.12 to 0.13

2010-10-13 Thread Wilson MacGyver
Great, time to buy 10 more macminis :) On Wed, Oct 13, 2010 at 1:34 PM, David Smith wrote: > To the best of my knowledge, there are no changes between 0.12->0.13 > that would prevent a rolling upgrade. That said, we have not tested > that specific use-case yet -- it's in the pipeline to be part o

Re: Upgrade procedure from 0.12 to 0.13

2010-10-13 Thread Alexander Sicular
Well it sounds to me that there are three primary considerations. Riak_core, Riak_kv and bitcask (assuming you are using that backend). If either of those change in some incompatible way you could end up doing damage to your data. I dunno, sounds possible to me. That said, rolling upgrades would

Re: Upgrade procedure from 0.12 to 0.13

2010-10-13 Thread Jesse Newland
I just used the new `riak-admin wait-for-service` command and some capistrano magic trick to do a rolling restart of all my nodes in production after installing the new debs. Worked like a charm. https://gist.github.com/48529d7eb1a9a69935fd Regards - Jesse Newland --- je...@railsmachine.com 40

Re: Upgrade procedure from 0.12 to 0.13

2010-10-13 Thread Wilson MacGyver
I thought it's possible to do "rolling upgrade". ie, shutdown 1 node, upgrade it, and reconnect the node to the cluster. otherwise you'd need 2X of the nodes in production. On Wed, Oct 13, 2010 at 1:21 PM, Alexander Sicular wrote: > I'm pretty sure that Baho would recommend that all nodes in a c

Re: Upgrade procedure from 0.12 to 0.13

2010-10-13 Thread Alexander Sicular
I'm pretty sure that Baho would recommend that all nodes in a cluster should be running the same version. An upgrade would probably require doing a full database backup and a full database restore on a *new* cluster. -Alexander On Oct 13, 2010, at 10:06 AM, SKester wrote: > Hey folks, > > Wh

Upgrade procedure from 0.12 to 0.13

2010-10-13 Thread SKester
Hey folks, What is the proper way to upgrade a cluster from 0.12 to 0.13? Our 4 node cluster was originally created by installing the 0.12 rpms. Is the process as simple as stopping riak on a node, installing the new rpm and re-starting? Is it possible to roll through each node one at a time w