05:35:26 GMT <kobzar> Hello !
05:36:17 GMT <kobzar> People! Help me do some with redis... I couldn't understand how a can do some action when key is expired :(
05:37:03 GMT <kobzar> For example, when key will expired in db0  - copy/add it(or some other) in db3
06:30:38 GMT <kobzar> %(
06:30:46 GMT <kobzar> No one can help me ?
07:52:04 GMT <badboy_> kobzar: you can't
07:52:08 GMT <badboy_> Redis has no hooks for that
07:52:37 GMT <kobzar> maybe you are have a good idea for my question?
09:07:47 GMT <Habbie> kobzar, how about https://redis.io/topics/notifications ?
09:11:30 GMT <kobzar> yes. this is it. But i can't understand how i need use it to add new key when old key leased.
09:14:29 GMT <p1rate> is it possible to add a key to multiple sets at once?
09:15:29 GMT <p1rate> so not like "SADD key member [member ...]" but SADD member key key key
09:40:47 GMT <Habbie> p1rate, you could write a lua EVAL script to do it
09:56:18 GMT <p1rate> Habbie, yeah...I think I
09:56:22 GMT <p1rate> Ill just do that
09:59:58 GMT <yac> Is redis 2.4.10 (currently available on CentOS 6) still reasonably usable?
10:53:06 GMT <Dirkos> Can anyone help me to get redis-cli running in RHEL
11:31:44 GMT <kobzar> what the problem Dirkos/
11:31:45 GMT <kobzar> ?
11:55:27 GMT <Dirkos> kobzar: well redis-cli is that avaialble as a package?
11:55:31 GMT <Dirkos> Since i want to flush varnish from remote server
11:55:40 GMT <Dirkos> I know it is in ubuntu but cannot find it in RHEL7
11:56:21 GMT <kobzar> Didi you added epel repository before search the package?
11:58:35 GMT <kobzar> `--# whereis redis-cli
11:58:39 GMT <kobzar> And what the result by for example
11:58:44 GMT <kobzar> redis-cli: /usr/bin/redis-cli
12:23:15 GMT <Dirkos> kobzar: there is no redis-cli on the server
12:23:17 GMT <Dirkos> but i need to get it
12:32:44 GMT <kobzar> what the result on command "yum list installed|grep redis"
12:34:04 GMT <kobzar> Also, you an install it manual from git https://github.com/holys/redis-cli or get it from source
12:34:19 GMT <kobzar> Something like this
12:34:22 GMT <kobzar> cd /tmp
12:34:22 GMT <kobzar> wget http://download.redis.io/redis-stable.tar.gz
12:34:22 GMT <kobzar> tar xvzf redis-stable.tar.gz
12:34:24 GMT <kobzar> cd redis-stable
12:34:26 GMT <kobzar> make
12:34:28 GMT <kobzar> cp src/redis-cli /usr/local/bin/
12:34:30 GMT <kobzar> chmod 755 /usr/local/bin/redis-cli
13:27:46 GMT <minus> `LDFLAGS=-static make` if you want a static build that you can copy on any linux machine
13:28:01 GMT <minus> (might need to `make distclean` before)
15:25:06 GMT <korishev> can anybody help me "cluster forget" a node that is stuck in handshake?  Amazon _killed the server_ and I can't get rid of the node records...
16:58:08 GMT <nnog> is slaveof replication not supported with a v3.2.2 slave against a v4.0.0 master? I thought the idea of psync/replconf meant compatibility in this regard... I guess just not forward compatibility
18:22:58 GMT <minus> 4.0 has new psync, dunno if it kept the old one
19:27:14 GMT <mbffff> I am using redis as a session store. sessionId -> userId. This allows for multiple sessions by the same user, which is intentional. However I'd like like to delete all the sessions for a user when a user changes their password. How would I go about this?
19:55:05 GMT <minus> mbffff: you store the reverse information too
19:55:33 GMT <minus> mbffff: e.g. a set `sessions:<userid>` with session ids as members
19:58:10 GMT <mbffff> minus: ok how would I handle expires? expires with just sessionId -> userId is easy, however if data is duplicated, I am imagine it isn't?
19:58:47 GMT <minus> true
19:58:47 GMT <badboy_> nnog: the rdb format changed in v4
19:59:45 GMT <minus> mbffff: you /could/ list all user sessions and search through them to kill the ones for the user, but that's very bad, performance-wise
20:00:57 GMT <mbffff> that was my thought, as a user doesn't change their password that often. But does scan/match only work with keys? I want to scan and match on a value
20:00:58 GMT <minus> mbffff: another option is to store the session ids in a sorted set, using the current timestamp as score and removing those whose timestamp is too old periodically with an external tool
20:01:13 GMT <minus> mbffff: just keys
20:01:32 GMT <minus> you'd essentially have to list all keys, fetch every single one of them and check them
20:01:40 GMT <mbffff> so I would need to search on the application side?
20:02:02 GMT <minus> yes
20:02:51 GMT <minus> you can also have a daemon listen to key expiry events and… then do nothing because it doesn't know the userid
20:03:41 GMT <mbffff> hmmm your other suggestion sounds awful difficult to get right... I was hoping that redis /w expires would simplify my user mgmt. I may need to just still with Postgres and index on key AND value
20:03:55 GMT <mbffff> stick with*
20:05:12 GMT <minus> i wonder if a postgres table with foreign data wrapper to redis would be of any use
20:05:20 GMT <minus> probably not
20:05:40 GMT <mbffff> the downside to PG is there isn't a great way to do expires.
20:05:53 GMT <mbffff> redis has SETEX and TOUCH.
20:06:31 GMT <minus> aye, in postgres you do need an external expirator
20:07:26 GMT <mbffff> alternatively I could design my app to only allow 1 session per user. But gmail seems to pull it off a scale. If someone logs in on there phone It would be stupid to log them out on the desktop
20:07:59 GMT <minus> well, they also have put a lot of work into that, i suppose
20:09:09 GMT <mbffff> yeah, you can see the IP and other info for each session too with gmail.