Re: Recovering Riak data if it can no longer load in memory

2016-07-13 Thread Vikram Lalit
Many thanks again, Matthew... this is very educative and helpful...! I'm now giving a shot with higher performance nodes... Thanks again! On Tue, Jul 12, 2016 at 4:18 PM, Matthew Von-Maszewski wrote: > You can further reduce memory used by leveldb with the following setting > in riak.conf: > >

Re: Recovering Riak data if it can no longer load in memory

2016-07-12 Thread Matthew Von-Maszewski
You can further reduce memory used by leveldb with the following setting in riak.conf: leveldb.threads = 5 The value "5" needs to be a prime number. The system defaults to 71. Many Linux implementations will allocate 8Mbytes per thread for stack. So bunches of threads lead to bunches of

Re: Recovering Riak data if it can no longer load in memory

2016-07-12 Thread Vikram Lalit
Thanks much Matthew. Yes the server is low-memory given only development right now - I'm using an AWS micro instance, so 1 GB RAM and 1 vCPU. Thanks for the tip - let me try move the manifest file to a larger instance and see how that works. More than reducing the memory footprint in dev, my conce

Re: Recovering Riak data if it can no longer load in memory

2016-07-12 Thread Matthew Von-Maszewski
It would be helpful if you described the physical characteristics of the servers: memory size, logical cpu count, etc. Google created leveldb to be highly reliable in the face of crashes. If it is not restarting, that suggests to me that you have a low memory condition that is not able to loa