Re: Riak CS: avoiding RAM overflow and OOM killer

2016-11-28 Thread Daniel Miller
Hi Alexander, Thanks a lot for your input. I have a few follow-up questions. > Stupid math: > > 3e7 x 3 (replication) / 9 = 1e7 minimum objects per node ( absolutely more > due to obj > 1MB size ) > > 1e7 x ~400 bytes per obj in ram = 4e9 ram per node just for bitcask. Aka 4 > GB. > > You alread

Re: Riak CS: avoiding RAM overflow and OOM killer

2016-11-23 Thread Alexander Sicular
Hello DeadZen, Yes, networking interconnect becomes a bigger issue with more nodes in the cluster. A Riak cluster is actually a fully meshed network of erlang virtual machines. Multiple 1/10 gig nics dedicated to inter/intra networking are your friends. That said, we have many customers running

Re: Riak CS: avoiding RAM overflow and OOM killer

2016-11-23 Thread DeadZen
ok I loled at this. then got worries trump could win a node election. anyways. 24gigs per riak server is not a bad safe bet. Erlang in general is ram heavy. It uses it more effectively then most languages wrt concurrency, but ram is the fuel for concurrency and buffer for operations, especially du

Re: Riak CS: avoiding RAM overflow and OOM killer

2016-11-23 Thread Daniel Miller
Hi Alexander, Thanks for responding. > How many nodes? We currently have 9 nodes in our cluster. > How much ram per node? Each node has 4GB of ram and 4GB of swap. The memory levels (ram + swap) on each node are currently between 4GB and 5.5GB. > How many objects (files)? What is the average

Re: Riak CS: avoiding RAM overflow and OOM killer

2016-11-22 Thread Alexander Sicular
Hi Daniel, Ya, I'm not surprised you're having issues. 4GB ram is woefully underspecd. 😔 🤓Stupid math: 3e7 x 3 (replication) / 9 = 1e7 minimum objects per node ( absolutely more due to obj > 1MB size ) 1e7 x ~400 bytes per obj in ram = 4e9 ram per node just for bitcask. Aka 4 GB. You already

Re: Riak CS: avoiding RAM overflow and OOM killer

2016-11-21 Thread Alexander Sicular
Hi Daniel, How many nodes? -You should be using 5 minimum if you using the default config. There are reasons. How much ram per node? -As you noted, in Riak CS, 1MB file chunks are stored in bitcask. Their key names and some overhead consume memory. How many objects (files)? What is the average f

Re: Riak CS: avoiding RAM overflow and OOM killer

2016-11-21 Thread Daniel Miller
I found a similar question from over a year ago ( http://lists.basho.com/pipermail/riak-users_lists.basho.com/2015-July/017327.html), and it sounds like leveldb is the way to go, although possibly not well tested. Has anything changed with regard to Basho's (or anyone else) experience with using le

Riak CS: avoiding RAM overflow and OOM killer

2016-11-05 Thread Daniel Miller
Hi, I have a Riak CS cluster up and running, and am anticipating exponential growth in the number of key/value pairs over the next few years. From reading the documentation and experience, I've concluded that the default configuration of CS (with riak_cs_kv_multi_backend) keeps all keys in RAM. Th