| hmm … 128 partitions divide by 5 nodes is ~26 vnodes per server. AAE creates a parallel number of vnodes, so your servers have ~52 vnodes each. 52 x 3,000 is 156,000 files … 156,000 > 65,536 ulimit. Sooner or later 65,536 will be too small. But ... Now, the primary account method in 1.4.2 is memory size allocated based upon max_open_files. So you have allocated 4Mbytes x 3,000 x 52 or 624,000Mbytes of RAM for leveldb. If you truly have a 624Gbyte machine, sweet! Otherwise, it might be time to scale back the max_open_files … and put AAE back to its default because it does not need a high max_open_files. The tricky part to leveldb configuration is that the max_open_files parameter is per vnode / partition, not for the entire server. This per vnode setting has caused many to over allocate, and is mostly inconsistent with every other piece of software on a Linux server. (And caused a couple of justified rants on this user list.) A more sane approach is coming out in Riak 2.0. But until then, here is a spreadsheet that can help planning: |
leveldb_sizing_1.4.xls
Description: Binary data
Matthew On Nov 11, 2013, at 2:56 PM, Dave Brady <[email protected]> wrote:
|
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
