Migrating to riak 2.1.4, selecting a specific multi-backend from the Java Client

Henning Verbeek hankipanky at gmail.com
Wed Aug 10 03:50:36 EDT 2016

Hi Magnus,

On Wed, Aug 10, 2016 at 9:21 AM, Magnus Kessler <mkessler at basho.com> wrote:
> On 9 August 2016 at 15:42, Henning Verbeek <hankipanky at gmail.com> wrote:
>> We're slowly migrating our application from Riak KV 1.4 to Riak KV
>> 2.1.4, and at the same time riak-java-client 1.4.x to riak-java-client
>> 2.0.6. We are doing this by adding seven new Riak KV 2.1 nodes to the
>> ring, and later removing the seven Riak KV 1.4 nodes from the ring.
>> For a few days, the cluster will consist of a mix.
> This plan will generate a lot of unnecessary data shuffling in the entire
> cluster. Each time a node is added or removed from the ring, the claim
> algorithm will re-assign partitions to/from all nodes. Please consider
> updating the existing nodes in place.

Thanks. We anticipated that, and it's basically two ring changes (add
all new nodes, remove all old nodes). The balancing takes about 12h
for the 15TB or so to get redistributed. We've taken this opportunity
to move our data onto newer, bigger machines that have become
available at our hosting provider.


More information about the riak-users mailing list