Thanks Nico. I'll make the changes you suggest to regain the consistency.
My understanding is a ring size of 64 would limit my cluster to about 6
nodes, right?
Jim
From: Nico Meyer <nico.me...@adition.com>
Date: Sat, 22 Oct 2011 12:12:13 +0200
To: "riak-users@lists.basho.com" <riak-users@lists.basho.com>, Jim Adler
<jim.ad...@comcast.net>
Subject: Re: Riak 1.0
Hello Jim,
it sounds like the ring_creation_size in your app.conf file is inconsistent
with the actual ring size on your existing nodes. This would happen, if the
ring_creation_size in the config was changed after the ring as been created.
As the name implies, the setting is only used when starting a fresh/empty
node for the first time, so changing it afterwards has no real effect, other
than showing up in the riak-admin output and severly confusing people ;-).
So to fix your problem, first of all, since the real ring size is 64, your
new node must also have a ring size of 64. So do as Dan suggested, but set
the ring_creation_size to 64 instead of 256.
At that point joining might already work. I checked the code, and if the
new gossip protocol is used, riak checks for equality the actual ring sizes
of the two nodes to join. But if the legacy gossip protocol is still used,
riak compares the ring_creation_size config settings of both nodes.
In any case, you should change the ring_creation_size on all your nodes to
64 and restart them, if only to make thing consistent again.
Cheers,
Nico
Am 22.10.2011 09:46, schrieb Jim Adler:
>
> For the bitcask backend, ring_num_partitions=64 and ring_creation_size=256. I
> haven't seen where to set ring_num_partitions in app.config. I have about 8
> million keys stored in this cluster.
>
>
>
>
> So, how do I bring up a LevelDB node and join to the existing cluster given
> this 64/256 partitions/creation_size config?
>
>
>
>
> Thanks for the help!
>
>
>
>
> Jim
>
>
>
>
> From: Dan Reverri <d...@basho.com>
> Date: Fri, 21 Oct 2011 09:41:02 -0700
> To: Jim Adler <jim.ad...@comcast.net>
> Cc: Ian Plosker <i...@basho.com>, "riak-users@lists.basho.com"
> <riak-users@lists.basho.com>
> Subject: Re: Riak 1.0
>
>
>
>
> The "ring_creation_size" parameter in app.config must be set before the node
> has been started and written a ring file. Assuming the LevelDB node is empty,
> you can do the following:
>
>
>
> 1. Stop the node
>
> 2. Clear out the data directories (data/ring, data/leveldb, data/bitcask,
> data/mr_queue, data/kv_vnode)
>
> 3. Verify "ring_creation_size" is set to 256 in the app.config file
>
> 4. Start the node
>
> 5. Verify "ring_num_partitions" in "riak-admin status" is 256
>
> 6. Join the node to the cluster
>
>
>
>
> Thanks,
>
> Dan
>
> Daniel Reverri
> Developer Advocate
> Basho Technologies, Inc.
> d...@basho.com
>
>
>
> On Fri, Oct 21, 2011 at 9:30 AM, <jim.ad...@comcast.net> wrote:
>
>>
>>
>>
>>
>> 64 on the LevelDB vs 256 on the Bitcask. I guess that’s it. Workaround?
>>
>>
>>
>> Thanks,
>>
>> Jim
>>
>>
>>
>> From: Dan Reverri [mailto:d...@basho.com]
>> Sent: Friday, October 21, 2011 9:27 AM
>> To: Jim Adler
>> Cc: Ian Plosker; riak-users
>> Subject: Re: Riak 1.0
>>
>>
>>
>>
>>
>>
>> Hi Jim,
>>
>>
>>
>>
>>
>>
>>
>>
>> Can you check "ring_num_partitions" on each node from "riak-admin status"?
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Thanks,
>> Dan
>>
>>
>>
>>
>>
>> Daniel Reverri
>> Developer Advocate
>> Basho Technologies, Inc.
>> d...@basho.com
>>
>>
>>
>>
>>
>> 2011/10/20 Jim Adler <jad...@intelius.com>
>>
>>
>>
>>
>> I tried the Bitcask-to-LevelDB procedure on 1.0.1 to switch my backend from
>> Bitcask to LevelDB. I have one node on Bitcask with my data and the other
>> node with a fresh LevelDB backend. When I join the fresh LevelDB node, I get
>> the following error: Failed: r...@xx.xx.xx.xx has a different
>> ring_creation_size
>>
>>
>>
>> riak-admin status | grep creation gives: ring_creation_size : 256
>>
>>
>>
>> Any ideas?
>>
>>
>>
>> Jim
>>
>>
>>
>>
>>
>>
>> From: riak-users-boun...@lists.basho.com
>> [mailto:riak-users-boun...@lists.basho.com] On Behalf Of Ian Plosker
>> Sent: Saturday, October 01, 2011 8:15 AM
>> To: 54chen
>> ! Cc: riak-users
>> Subject: Re: Riak 1.0
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> There are instructions on the wiki:
>> http://wiki.basho.com/Secondary-Indexes.html#Migrating-an-Existing-Cluster-(M
>> ethod-One)
>> <http://wiki.basho.com/Secondary-Indexes.html#Migrating-an-Existing-Cluster-%
>> 28Method-One%29>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Basically, you will have each node leave the cluster, switch the backend, and
>> then rejoin. The process is something like this:
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> 1) Issue `riak-admin leave` and wait for all transfers to complete
>>
>>
>>
>>
>> 2) `riak stop`
>>
>>
>>
>>
>> 3) Change the backend to the `riak_kv_eleveldb_backend`
>>
>>
>>
>>
>> 4) `riak start` and `riak-admin join <a_node>`
>>
>>
>>
>>
>> 5) Repeat for each node in the cluster
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Ian Plosker
>>
>>
>>
>>
>> Developer Advocate
>>
>>
>>
>>
>> Basho Technologies
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Sep 30, 2011, at 10:41 PM, 54chen wrote:
>>
>>
>>
>>
>>
>> Congratulations!
>>
>> Can you give me an example of how the 0.14.2（bitcas! k） upgrade to 1.0（
>> levelDB）?
>>
>>
>>
>>
>>
>>
>>
>> 2011/10/1 Alexander Sicular <sicul...@gmail.com>
>>
>> Awesome!
>>
>> Already got it in place on my mac and ubuntu dev boxes. Smooth.
>>
>> -Alexander Sicular
>>
>> @siculars
>> http://siculars.posterous.com <http://siculars.posterous.com/>
>>
>>
>>
>>
>>
>> On Sep 30, 2011, at 4:31 PM, David Smith wrote:
>>
>>> > Hi All,
>>> >
>>> > I am very pleased to announce that Riak 1.0 is tagged and officially
>>> > ready for downloading.
>>> >
>>> > Pre-built installations and source tarballs are available at:
>>> >
>>> > http://downloads.basho.com/riak/CURRENT
>>> >
>>> > Release notes are here:
>>> >
>>> > https://github.com/basho/riak/blob/1.0/RELEASE-NOTES.org
>>> <https://github.com/basho/riak/blob/1.0/RELE%21%20ASE-NOTES.org>
>>> >
>>> > There is also a blog post about the release here:
>>> >
>>> > http://blog.basho.com/2011/09/30/Riak-1-dot-0-is-Official/
>>> >
>>> > 1.0 has been two years and 15 releases in the making. Thank you all
>>> > for being a part of this project and wonderful community. We couldn't
>>> > have done it without you.
>>> >
>>> > Sincerely,
>>> >
>>> > D.
>>> >
>>> > --
>>> > Dave Smith
>>> > Director, Engineering
>>> > Basho Technologies, Inc.
>>> > diz...@basho.com
>>> >
>>> > _______________________________________________
>>> > riak-users mailing list
>>> > riak-users@lists.basho.com
>>> > http://lists.basho.com/mailman/listinfo/riak-users _lists.basho.com
>>> <http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.c%21%20om>
>>
>>
>> _______________________________________________
>> riak-users mailing list
>> riak-users@lists.basho.com
>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>>
>>
>>
>>
>>
>>
>>
>> --
>> -
>> http://www.54chen.com <http://www.54chen.com/>
>> http://twitter.com/54chen
>> _______________________________________________
>> 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.comhttp://lists.basho.com/mailman/listinfo/riak-users_l
> ists.basho.com
>
_______________________________________________
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
