Riak ring size
john at kavanista.com
Thu Oct 3 12:18:00 EDT 2013
Thanks Matthew , we are actually using Bitcask with 128Gb RAM per node.
On 3 Oct 2013, at 17:10, Matthew Von-Maszewski <matthewv at basho.com> wrote:
If you are using leveldb as Riak's backend, keep in mind that each vnode requires a fixed amount of memory (set via max_open_files and cache_size in app.config). Recently had one user attempt too many vnodes on a 4Gbyte machine. He populated data to the point of memory overflow … then migration out of that mess took days.
> On Oct 3, 2013, at 11:52 AM, John Kavanagh <john at kavanista.com> wrote:
> Thanks Sean !
>> On Thu, Oct 3, 2013 at 4:33 PM, Sean Cribbs <sean at basho.com> wrote:
>> Hi John,
>> Our rule-of-thumb is 8-64 partitions per physical node, so a good starting point for a 6-node cluster would be 128 or 256. 256 will let you expand up to about 30 nodes without needing a ring resize.
>>> On Thu, Oct 3, 2013 at 10:14 AM, John Kavanagh <john at kavanista.com> wrote:
>>> Hi all,
>>> I'm trying to understand the optimal ring size / vnode config for a 6 node Riak cluster, which will most likely expand to many more nodes over time . Does everyone bump from the default of 64 to 1024 to facilitate future growth ? I can provide more detailed capacity metrics off list if necessary.
>>> riak-users mailing list
>>> riak-users at lists.basho.com
>> Sean Cribbs <sean at basho.com>
>> Software Engineer
>> Basho Technologies, Inc.
> riak-users mailing list
> riak-users at lists.basho.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the riak-users