{"action":"opened","issue":{"url":"https://api.github.com/repos/dieterich-lab/webdorina/issues/16","labels_url":"https://api.github.com/repos/dieterich-lab/webdorina/issues/16/labels{/name}","comments_url":"https://api.github.com/repos/dieterich-lab/webdorina/issues/16/comments","events_url":"https://api.github.com/repos/dieterich-lab/webdorina/issues/16/events","html_url":"https://github.com/dieterich-lab/webdorina/issues/16","id":53621718,"number":16,"title":"redis cache runs full","user":{"login":"rekado","id":47740,"avatar_url":"https://avatars.githubusercontent.com/u/47740?v=3","gravatar_id":"","url":"https://api.github.com/users/rekado","html_url":"https://github.com/rekado","followers_url":"https://api.github.com/users/rekado/followers","following_url":"https://api.github.com/users/rekado/following{/other_user}","gists_url":"https://api.github.com/users/rekado/gists{/gist_id}","starred_url":"https://api.github.com/users/rekado/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rekado/subscriptions","organizations_url":"https://api.github.com/users/rekado/orgs","repos_url":"https://api.github.com/users/rekado/repos","events_url":"https://api.github.com/users/rekado/events{/privacy}","received_events_url":"https://api.github.com/users/rekado/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-01-07T11:11:39Z","updated_at":"2015-01-07T11:11:39Z","closed_at":null,"body":"We ran into a problem where redis exhausted the host system's memory completely.  Restarting redis-server did not help as stopping the server involves serialising the cache contents to disk.  Upon restart the serialised data is read back into memory leading to swapping / thrashing.  Once we realised what was going on the fix was to run `redis-cli FLUSHALL` to flush the cache.\r\n\r\nI think it's the application's responsibility to clean out old records from the in-memory cache when storing new results would bring the memory consumption close to MAX/2 (at which point redis becomes less performant).  I see that cache records have a TTL already.  Is the TTL acted upon by any of the storage methods to purge old records in favour of new results?"}}