Hi Mojito,

At the moment, changing the ring_creation_size parameter is not an easy
process. It's important to choose a number that is large enough that you
will not need to change it for a really long time. Projects will typically
define an upper bound for a cluster's size based on available datacenter
space, available power, cost, etc. Choosing a ring_creation_size value based
on this upper bound will allow you to start small and grow into your
cluster.

Changing the ring_creation_size, right now, requires building a new cluster
with the new ring_creation_size value and migrating data from the old
cluster (backup and restore).

Thanks,
Dan

Daniel Reverri
Developer Advocate
Basho Technologies, Inc.
d...@basho.com


On Thu, Sep 30, 2010 at 5:01 PM, Mojito Sorbet <mojitot...@gmail.com> wrote:

> What if your DB continues to grow beyond the original design size and
> you need to add a lot more nodes?
>
> On Thu, 2010-09-30 at 16:34 -0700, Dan Reverri wrote:
> > Yes, that is true.
> >
> > Daniel Reverri
> > Developer Advocate
> > Basho Technologies, Inc.
> > d...@basho.com
> >
> >
> > On Thu, Sep 30, 2010 at 4:27 PM, Alexander Sicular
> > <sicul...@gmail.com> wrote:
> >         Dan,
> >         Is it true that "ring_creation_size" should only be altered at
> >         the creation of a cluster? Once you already have physical
> >         nodes in a cluster you shouldn't adjust the
> >         "ring_creation_size". True?
> >
> >
> >         Thanks, Alexander.
> >
> >
> >
> >         @siculars on twitter
> >         http://siculars.posterous.com
> >
> >
> >         Sent from my iPhone
> >
> >
> >         On Sep 30, 2010, at 19:16, Dan Reverri <d...@basho.com> wrote:
> >
> >
> >
> >         > Hi Michael,
> >         >
> >         >
> >         > There is no hard coded limit to the number of nodes that can
> >         > belong to a cluster. Depending on how quickly you are adding
> >         > nodes to the cluster you may be running into an issue with
> >         > the ring not converging on a single state.
> >         >
> >         >
> >         > Can you try using the "riak-admin ringready" command between
> >         > each join of a node? This command will return TRUE if the
> >         > nodes all agree on a particular ring state. You should run
> >         > this command until it returns TRUE after each join.
> >         >
> >         >
> >         > Also, Alexander is correct; you should deploy your nodes
> >         > with an increased value for the "ring_creation_size"
> >         > parameter in app.config. The typical recommendation is to
> >         > have a minimum of 10 partitions per node and the value
> >         > should be a power of 2 (64, 128, 256, 512, 1024). For a 63
> >         > node cluster a value of 1024 would work well.
> >         >
> >         >
> >         > Thanks,
> >         > Dan
> >         >
> >         > Daniel Reverri
> >         > Developer Advocate
> >         > Basho Technologies, Inc.
> >         > d...@basho.com
> >         >
> >         >
> >         > On Thu, Sep 30, 2010 at 12:02 PM, Alexander Sicular
> >         > <sicul...@gmail.com> wrote:
> >         >         The default vnode number is 64. If you are
> >         >         connecting 63 physical nodes togeter in one riak
> >         >         cluster than you really want to increase the number
> >         >         of vnodes. There is some recommended metric for
> >         >         physical nodes to vnodes. I think it's like a
> >         >         minimum of 4 vnodes per physical node. But I could
> >         >         be totally making that up.
> >         >
> >         >
> >         >         -Alexander.
> >         >
> >         >
> >         >
> >         >         @siculars on twitter
> >         >         http://siculars.posterous.com
> >         >
> >         >
> >         >         Sent from my iPhone
> >         >
> >         >
> >         >         On Sep 30, 2010, at 14:26, Michael Colussi
> >         >         <mcolu...@gmail.com> wrote:
> >         >
> >         >
> >         >
> >         >         > Hey guys,
> >         >         >
> >         >         >
> >         >         > My team was trying to launch a 63 node Riak
> >         >         > cluster yesterday, using version 0.13rc3 and the
> >         >         > bitcask backend.
> >         >         >
> >         >         >
> >         >         > All 63 nodes agreed that the ring consisted of
> >         >         > nodes 1-42 only.
> >         >         >
> >         >         >
> >         >         > Any ideas?  Is there a hardcoded limit to the
> >         >         > number of nodes allowed?
> >         >         > _______________________________________________
> >         >         > 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.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.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

Reply via email to