02:14:53 GMT <heidi644> n00b redis question, I am building a 2..n autoscaling server sent event server, and I want to keep track of all the connections monitors by “visitor ID”.  Adding/Removing connection ids as visitors come and go is straight forward.  How best to account for when a server would suddenly die or be removed from auto scale group?  Set expiration time on keys?
11:44:19 GMT <kaushal> Hi
11:45:18 GMT <kaushal> I have set up redis 3.2.0 in Master ( VM1) and Slave mode (VM2). Do i need to configure both Master and Slave IP in my client config?
11:45:41 GMT <kaushal> For example if the Master goes down the Slave will serve the request
11:45:55 GMT <kaushal> Any suggestions please?
11:58:56 GMT <kaushal> Anyone around here?
12:35:54 GMT <minus> any thoughts on Apache Storm or Bucardo for replicating data from Postgres to Redis?
13:28:09 GMT <itamarhaber> _SLM_: thanks for spotting this, post updated with the impact of https://github.com/uglide/RedisDesktopManager/commit/7ff4f5ce7bc4465d4c20af7c0e74ea2e9d344358
16:12:00 GMT <nnog> Has anyone here had an issue with Sentinel leader election/failover repeatedly refusing to failover?
16:13:26 GMT <nnog> I have 3 sentinels, I kill the master, I get the +odown, I get +vote-for-leader in all 3, and -failover-abort-not-elected master in 2
16:13:45 GMT <nnog> which is all good so far, then just Next failover delay: I will not start a failover before ...
16:14:09 GMT <nnog> repeatedly. +new-epoch's then it just repeats
16:14:23 GMT <nnog> every 6 mins or so
16:14:49 GMT <nnog> I'm running 3.2.0
16:15:11 GMT <nnog> and have quorum of 2/3
16:15:33 GMT <nnog> so I get +odown master Test 164.xx.xx.xxx 6509 #quorum 3/2
16:16:21 GMT <nnog> but never enters failover...
17:52:55 GMT <chrstphrhrt> hi peeps, I'm trying to use PSUBSCRIBE key:pattern:*:with:*:globs but am not seeing any events in the client despite CONFIG GET notify-keyspace-events showing AKE
17:52:57 GMT <chrstphrhrt> ideas?
17:53:38 GMT <chrstphrhrt> (but i know there are HSETs going on to the keys in question)
19:42:53 GMT <chrstphrhrt> i'm doing a PSUBSCRIBE in redis-cli and getitng the expected output https://gist.github.com/chrstphrhrt/991236cbd7eeba22a6199237e2224dbd
19:43:09 GMT <chrstphrhrt> however, when connecting from any other client, I'm only seeing the last line
19:43:26 GMT <chrstphrhrt> as in, not #1-3 from the cli output
19:43:57 GMT <chrstphrhrt> is there a way to customize this?
20:53:04 GMT <madsage> greets
20:54:58 GMT <madsage> question. should 3.2 work okay with an older windows connector previous working with 2.8.4, one would expect backwards compat?
20:57:29 GMT <madsage> i built a cluster with 3.2 I brought it up and immediatly had keyshare mismatch issues in logfile. had to revert back to 2.8.4. I cant really update the connector as we have code from that SDK built into application.
20:57:31 GMT <minus> madsage: the client protocol did not change (i think, read the changelog)
20:58:14 GMT <minus> okay, no idea about cluster
20:58:38 GMT <madsage> yeah, nothing really stood out at me. i'll go through it again.
20:58:53 GMT <madsage> thanks
21:04:42 GMT <madsage> hmm..  Redis 2.8 is mostly a strict subset of 3.0, you should not have any problem upgrading your application from 2.8 to 3.0
21:05:08 GMT <madsage> and says the same for 3.0 to 3.2
21:05:18 GMT <madsage> interesting
21:06:39 GMT <madsage> ok, think i' well bring 3.2 up next to 2.8 do some testing again.  I had to change views to another part of the project. moving back to 2.8 bought me some time
21:06:55 GMT <madsage> s/well/will
21:07:44 GMT <madsage> i want the improved cluster features
21:13:08 GMT <joaquins> hi, some has tryied Redis as a queue system like RabbitMQ?
21:13:31 GMT <joaquins> someone*
21:18:59 GMT <dvirsky> joaquins, yes it's a very popular use case for redis. e.g. resque https://github.com/resque/resque
21:43:39 GMT <madsage> rabbit-MQ
21:43:46 GMT <madsage> <3
23:11:58 GMT <mdw> hey people
23:12:09 GMT <mdw> I've just started using Heroku Redis
23:12:26 GMT <mdw> I've just noticed my 'number of keys plummet from about 20, to zero'
23:12:31 GMT <mdw> what does this mean?
23:12:45 GMT <mdw> everything seems to be working fine
23:13:12 GMT <mdw> I've just noticed my 'number of keys plummet from about 20, to zero'
23:13:19 GMT <mdw> what does this mean?
23:13:26 GMT <mdw> 	I've just started using Heroku Redis
23:13:34 GMT <mdw> (repeating due to net split event)