Re: Object not found after successful PUT on S3 API

2017-04-28 Thread Magnus Kessler
On 28 April 2017 at 15:15, Matthew Von-Maszewski wrote: > Daniel, > > Something is wrong. All instances of leveldb within a node share the > total memory configuration. The memory is equally divided between all > active vnodes. It is possible to create an OOM situation if total RAM is > low an

Re: Object not found after successful PUT on S3 API

2017-04-28 Thread Matthew Von-Maszewski
Daniel, Something is wrong. All instances of leveldb within a node share the total memory configuration. The memory is equally divided between all active vnodes. It is possible to create an OOM situation if total RAM is low and vnodes count per node is high relative to RAM size. The best ne

Re: Object not found after successful PUT on S3 API

2017-04-28 Thread Daniel Miller
Hi Luke, I'm reviving this thread from March where we discussed a new backend configuration for our riak cluster. We have had a chance to test out the new recommended configuration, and so far we have not been successful in limiting the RAM usage of leveldb with multi_backend. We have tried variou