12:46:07 GMT <theonefoo> Hello, I have about 20-30 keys that have the following keyname: `service:resource:<id>`, where an example is `service:resource:12345`. What would be the correct way to get the values of all keys corresponding to `service:resource:*` where * means everything?
12:47:59 GMT <theonefoo> I’ve tried `GET service:resource:*` and `MGET service:resource:* which both return `(nil)`. I think I’m not understand how to format my query here
12:48:16 GMT <theonefoo> woops backtick brainfarts
12:50:03 GMT <theonefoo> Would I have to first call `KEYS service:resource:*` and iterate over those and call `GET <key>`? Or is there a shortcut?
14:11:00 GMT <Craig_> hi, ive started using redis for session storage for my web api, so that i can scale it easily to extra servers if needed. the problem i have is that i also need something similar for persistent storage of medium sized (1-2mb) files. preferably something open source that i can run on a server myself rather than a cloud service i have to subscribe to. can anyone here recommend such a solution?
14:11:09 GMT <Craig_> and btw, great job with redis. love it!
14:30:51 GMT <dupondje> Hi. Some quick question. If you restart redis, the memory usage should be around the same no? As it saves & loads the keys from disk again then?
15:20:29 GMT <applecrumble> Hello, I'm running redis in a docker container on kubernetes. If I have multiple Redis servers running, is there a way to configure redis to share information between copies of itselff?
15:20:57 GMT <applecrumble> In short, can two redis servers share information, so that no matter which I connect to, I can get the values I need?
17:31:38 GMT <on3pk> Hi.  I'm trying to do some calculations on weather data and I'm thinking redis would be a good in-memory store for the data which spans across multiple processes.  I have data from multiple sites, dates, and types.  Is redis designed to handle data like this?
17:34:32 GMT <minus> on3pk: could work; looks at the commands redis has and see if those would work for you
17:40:00 GMT <on3pk> minus: the best I came up with last night is having the keys be a combination of the date and site (eg 2017-10-12-YYC) and the values be hash set -- but I don't know if that's really the best way to do it
17:41:00 GMT <minus> if you're accessing them individually, sure
17:43:39 GMT <on3pk> I'll be doing calculations on +1 years worth of data, but I can't think of a better way to actually store it...
17:44:19 GMT <on3pk> Mainly because it's possible a parallel process is also using the same data, and I don't want to copies in ram...
17:54:00 GMT <minus> if you don't want to keep all data in RAM you should use redis
20:07:21 GMT <on3pk> Does redis have any sort of garbage collector for when keys expire or do they only go away when I try to access the key in the future?
20:08:25 GMT <minus> expirations are handled by a timer afaik
20:08:44 GMT <minus> maxmemory-based evictions are done when a new key is added afaik
21:43:30 GMT <JoKeR_> Hi
21:43:39 GMT <JoKeR_> AnyOne ?
21:44:39 GMT <JoKeR_> ;)
21:46:00 GMT <JoKeR_> How i can delete keys which start by a prefix ?
23:17:40 GMT <Necrosan> use a scan 0 match <yourshit>
23:17:46 GMT <Necrosan> then iterate
23:17:50 GMT <Necrosan> oh, he left