We haven't often dealt with repartitioning clusters, which is why I recommended a complete backup and restore. The behavior when trying to dynamically change the partition quantity is undefined. Honestly I don't know how the backend would affect it at all. As always, however, adding nodes will increase performance and fault tolerance. If you intend to grow your cluster, a larger partition count will ease the transition and provide a more even spread.
On Wednesday, May 5, 2010, Garrett Smith <[email protected]> wrote: > Sean, > > I apologize if this is readily available in the docs, faq, etc. (I > obviously missed if it is). > > When a cluster is repartitioned, e.g. as a result of adding or > removing vnodes, is one backend preferable to another? Does keeping > node size down help/hurt in terms of performance, reliability, etc? > > Garrett > > On Wed, May 5, 2010 at 7:05 AM, Sean Cribbs <[email protected]> wrote: >> Germain, >> >> It looks like you're filling up the dets tables -- which have a 2GB limit >> per file, although Riak uses multiple files, one per vnode. Have you tried >> the innostore backend? Also if you continue to use dets, try increasing the >> number of partitions, which will make more, smaller files. >> >> Sean Cribbs <[email protected]> >> Developer Advocate >> Basho Technologies, Inc. >> http://basho.com/ > _______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
