09:04:01 GMT hi 09:05:27 GMT could somebody clarify several questions about Redis Keyspace Notifications? 09:05:57 GMT common practice in IRC - just ask your questions and wait. 09:06:18 GMT ok 09:08:26 GMT I'm using redis as distributed cache and I'm using pub/sub to send notifications about del, set, expired and evicted events. I have different applications which listen notifications using following patterns: App1.* App2.* 09:09:13 GMT to send notifications I use following property in redis.conf: notify-keyspace-events "AK" 09:09:29 GMT And it works fine for me, but.. 09:09:55 GMT but in this case of "AK" configuration redis starts to send extra notifications like "expire" which I don't need. 09:10:20 GMT so I have tries to specify custom property like: notify-keyspace-events "Ksxe" 09:11:56 GMT or "Ks" or even "Kg$lshzxe" and none of these configurations doesn't works correctly 09:12:28 GMT in case of "Ksxe" I receive only expired events 09:12:59 GMT in case of "Ks" I doesn't receive set events.. 09:14:45 GMT can somebody tell me why I doesn't receive set and evicted events?? Why I receive only expired events? 09:15:02 GMT and is there any way to make redis send only del notifications?? 09:15:12 GMT thanks 10:27:10 GMT hi! I am running pootle and it needs running rq worker. How I can can monitor from command line that a worker is running ? 10:28:58 GMT I have read out redis-cli commands, but nothing seems to match.. 10:54:35 GMT redis-cli monitor? 10:57:44 GMT I have checked the output of 'redis-cli monitor', but didn't noticed that workers would be listed there. Have I missed something ? 11:40:35 GMT ah. seems that rqworker is listed in process list 'ps -ef | rqworker'. I am happy for that. 14:43:08 GMT in a pub/sub when subscriber drops connection, and publisher is still publishing to that subscription, will the messages get queued or dropped? 14:46:15 GMT how do i make the connection redis persist those messages 15:18:15 GMT samof76: messages get dropped when the client disconnects/loses connection. no direct way to persist them; you'd have to build something of your own there 19:01:43 GMT Anyone know why redic-cli on windows would return an obsolete value for a key that i've updated using a node app? when the node app gets the value for the same key, it correctly returns the updated value. 19:02:55 GMT windows command i'm running is `redis-cli -h [hostname] -p [port] GET [key]` 19:07:21 GMT connecting to the wrong host with either of those two clients is the most likely explanation 19:14:41 GMT oog. i found it. bug in the node app was causing the writes to a similar key, but not the one i was checking. 19:17:52 GMT fair enough