Re: Memory-backend TTL

Hi Juan, Please see: https://github.com/basho/riak_kv/issues/1064 I have also forwarded this on internally. -- Luke Bakken Engineer / CSE lbak...@basho.com On Tue, Dec 16, 2014 at 10:52 AM, Juan Luis Francés wrote: > Hello. > > Do you have any update about this issue? I am affected by the sam

Re: Memory-backend TTL

Hello. Do you have any update about this issue? I am affected by the same memory leak. Sadly, this problem does the Riak memory backend useless in production. You can reproduce it with this dirty script (be careful, it is resource intensive): https://gist.github.com/indpnday/76d99c5852e0100c5a

Re: Memory-backend TTL

Hi Lucas, You can get the MIME type by retrieving one value via curl - curl -vvv -XGET -o data.bin localhost:8098/buckets/ttl_stg/keys/KEY Replace "KEY" with an actual key. Please attach the output and the "data.bin" file. I can use this to try and reproduce your memory consumption issue. -- Luk

Re: Memory-backend TTL

Sorry, I don't know the MIME type I used. I use the python api with default options. The doc says "string"? http://basho.github.io/riak-python-client/object.html#riak.riak_object.RiakObject.encoded_data 2014-10-20 15:43 GMT+02:00 Luke Bakken : > Lucas, > > Thanks for all the detailed informatio

Re: Memory-backend TTL

Lucas, Thanks for all the detailed information. This is not expected behavior. What MIME type are you using for storing the long integer data (64 binary bits, I assume)? I'd like to try and reproduce this. There have been issues with TTL and max_memory but they should have been fixed for Riak 2.0

Re: Memory-backend TTL

Hi Luke, Indeed, when removed the thousands of requests, the memory is stabilized. However the memory consumption is still very high: riak-admin status |grep memory memory_total : 18494760128 memory_processes : 145363184 memory_processes_used : 142886424 memory_system : 18349396944 memory_atom :

Re: Memory-backend TTL

Hi Luke. An update about the memory consumption in my 1 server "cluster" after about 10 hours after my last email. Remember, with max_memory_per_vnode = 250MB and ring_size=16. Sadly, I had to restart the riak daemon: # riak-admin diag -d debug [debug] Local RPC: os:getpid([]) [5000] [debug] Runn

Re: Memory-backend TTL

Hi Luke. I really appreciate your efforts to attempt to reproduce the problem. I think that the configs are right. I have been doing also a lot of tests and with 1 server/node, the memory bucket works flawlessly, as your test. The Riak cluster where we have the problem has a multi_backend with 1 m

Re: Memory-backend TTL

Hi Lucas, I've tried reproducing this using a local Riak 2.0.1 node, however TTL is working as expected. Here is the configuration I have in /etc/riak/riak.conf: storage_backend = multi multi_backend.default = bc_default multi_backend.ttl_stg.storage_backend = memory multi_backend.ttl_stg.memor

Re: Memory-backend TTL

Hi Luke. curl -vvv -XGET "http://localhost:8098/riak/ttl_stg/props"; * Hostname was NOT found in DNS cache * Trying 127.0.0.1... * Connected to localhost (127.0.0.1) port 8098 (#0) > GET /riak/ttl_stg/props HTTP/1.1 > User-Agent: curl/7.35.0 > Host: localhost:8098 > Accept: */* > < HTTP/1.1 404

Re: Memory-backend TTL

Hi Lucas, Could you run the following curl statement and provide the full transcript of the command and response? curl -vvv -XGET "http://localhost:8098/riak/ttl_stg/props"; -- Luke Bakken Engineer / CSE lbak...@basho.com On Mon, Oct 6, 2014 at 8:55 AM, Lucas Grijander wrote: > Hi Luke, > > O

Re: Memory-backend TTL

Hi Luke, Of course. The request is a simple curl: curl -v -X GET "http://localhost:8098/riak/ttl_stg/KEY"; 2014-10-06 16:59 GMT+02:00 Luke Bakken : > Hi Lucas, > > Can you confirm that the bucket or bucket-type that contains the > object you're retrieving has been configured to use the "ttl_st

Re: Memory-backend TTL

Hi Lucas, Can you confirm that the bucket or bucket-type that contains the object you're retrieving has been configured to use the "ttl_stg" backend? -- Luke Bakken Engineer / CSE lbak...@basho.com On Fri, Oct 3, 2014 at 11:32 AM, Lucas Grijander wrote: > Hello, > > I have a memory backend in p

Memory-backend TTL

Hello, I have a memory backend in production with Riak 2.0.1, 4 servers and 256 vnodes. The servers have the same date and time. I have seen an odd performance with the ttl. This is the config: {<<"ttl_stg">>,riak_kv_memory_backend, [{ttl,90},{max_memory,25}]}, For examp

Re: Memory Backend TTL doesn't work

Thank you!! I've got it!! :) Then, if I started server with ring size 32, I need to change max_memory to 256(8192/32). Is it right? Chan. 2013. 10. 14., 오후 9:35, Alex Moore mailto:amo...@basho.com>> 작성: Hi Chan, Instead of: {storage_backend, riak_kv_memory_backend}, {memory_backend, [ {max_mem

Re: Memory Backend TTL doesn't work

Hi Chan, Instead of: {storage_backend, riak_kv_memory_backend},  {memory_backend, [  {max_memory, 8192},  {ttl, 1}  ]},  Try: {multi_backend_default, <<"expiring_memory_backend">>}, {multi_backend, [ {<<"expiring_memory_backend">>, riak_kv_memory_backend, [

Memory Backend TTL doesn't work

Hi~! I'm checking riak to use as a cache like memcached. But I found some strange situation. I set "ttl" like this to expire data, but failed. - {riak_kv, [ ... {storage_backend, riak_kv_memory_backend}, {memory_backend, [ {max_memory, 819