Re: How to cold (re)boot a cluster with already existing node data

I wasn't referring to a cluster replace. node name/reip change can be done on all offline nodes before starting them. They still have a cluster if you dont delete the ring data. Having done that you actually deleted the cluster, (but not the data) when all that occurred was an ip address change

Re: How to cold (re)boot a cluster with already existing node data

Two suggestions: 1. Use Riak-EE, and have two rings. When you do an update, copy over one ring to the other side after you do a "cold reboot" 2. Use the Riak Mesos Framework. Mesos is like K8s, but it has stateful storage primitives. (Link: https://github.com/basho-labs/riak-mesos) On Mon, Jun 6,

Re: How to cold (re)boot a cluster with already existing node data

On Mon, 6 Jun 2016 at 16:52 Alex Moore wrote: > Hi Jan, > > When you update the Kubernates nodes, do you have to do them all at once > or can they be done in a rolling fashion (one after another)? > Thnaks for your reply, sadly this is not possible. Kubernetes with GKE just

Re: How to cold (re)boot a cluster with already existing node data

> this might be helpful, an Omniti article. > https://omniti.com/seeds/migrating-riak-do-it-live > Thanks for this article, will be valuable for further managing riak in the cluster. > As to fixing this specific error. That iirc can be done doing a name > change in the ring to match your new

Re: How to cold (re)boot a cluster with already existing node data

Hi Jan, When you update the Kubernates nodes, do you have to do them all at once or can they be done in a rolling fashion (one after another)? If you can do them rolling-wise, you should be able to: For each node, one at a time: 1. Shut down Riak 2. Shutdown/restart/upgrade Kubernates 3. Start

Re: How to cold (re)boot a cluster with already existing node data

this might be helpful, an Omniti article. https://omniti.com/seeds/migrating-riak-do-it-live As to fixing this specific error. That iirc can be done doing a name change in the ring to match your new node name. renaming the node will make that orddict lookup succeed. Theres a supplied admin

How to cold (re)boot a cluster with already existing node data

Hi, we are using riak in a kuberentes cluster (on GKE). Sometimes it's necessary to reboot the complete cluster to update the kubernetes-nodes. This results in a complete shutdown of the riak cluster and the riak-nodes are rescheduled with a new IP. So how can I handle this situation? How can I