ring_creation_size & ring_partition_number error joining 2.1.3 node to 2.1.1 cluster

Sargun Dhillon sargun at sargun.me
Sun Mar 6 22:25:52 EST 2016


They're effectively equal

Sent from my iPhone

On Mar 6, 2016, at 17:32, Robert Latko <robert at lmi-global.com> wrote:

Hi all,

Found the problem/solution.

With the first cluster, I set it up with a ring size of 64. Prior to
loading data. I stopped the node(s), changed the ring size to 256, then
restarted.

Therefore, if I want to add a new node, I FIRST must start the node with a
ring size of 64, then stop it, change the conf for a ring size of 256, then
start, then stage, plan, and commit.

I am still not sure the relation ship with ring size and ring partitions.

Sincerely,

Robert



On 03/06/2016 02:10 PM, Robert Latko wrote:

Hi All,

I've got a cluster in 2.1.1 and was wanting to join a 2.1.3 node to it

I am getting the following error:

# ./bin/riak-admin cluster join a-backend at 10.0.0.199
Failed: a-backend at 10.0.0.199 has a different ring_creation_size

So... for the new 2.1.3
# ./bin/riak-admin status | grep ring
ring_creation_size : 256
ring_members : ['node-template at 10.0.0.54']
*ring_num_partitions : 256*
ring_ownership : <<"[{'node-template at 10.0.0.54',256}]"
<[%7B%27node-template at 10.0.0.54%27,256%7D]>>>
rings_reconciled : 0
rings_reconciled_total : 0

AND for node a-backend at 10.0.0.199
# ./bin/riak-admin status | grep ring
ring_creation_size : 256
ring_members : ['a-backend at 10.0.0.199',' <b-backend at 10.0.0.200>
b-backend at 10.0.0.200',
*ring_num_partitions : 64*
ring_ownership : <<"[{'b-backend at 10.0.0.200',13},\n
{'c-backend at 10.0.0.201',13},\n {'d-backend at 10.0.0.202',13},\n
{'e-backend at 10.0.0.203',12},\n {'a-backend at 10.0.0.199',13}]"
<[%7B%27b-backend at 10.0.0.200%27,13%7D,%5Cn%7B%27c-backend at 10.0.0.201%27,13%7D,%5Cn%7B%27d-backend at 10.0.0.202%27,13%7D,%5Cn%7B%27e-backend at 10.0.0.203%27,12%7D,%5Cn%7B%27a-backend at 10.0.0.199%27,13%7D]>
>>
rings_reconciled : 0
rings_reconciled_total : 32

The 'ring_num_partitions' are different which leaves me to believe this is
the cause.

A.) How do I increase the 'ring_num_partitions' to 256 in the 2.1.1
cluster� **OR**
B.) How do I decrease the 'ring_num_partitions' to 64 in the 2.1.3 node?

Any ideas? recommendations?


Thanks in advance,


Robert









_______________________________________________
riak-users mailing
listriak-users at lists.basho.comhttp://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com


_______________________________________________
riak-users mailing list
riak-users at lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.basho.com/pipermail/riak-users_lists.basho.com/attachments/20160306/07e51f8f/attachment-0002.html>


More information about the riak-users mailing list