12:01:17 GMT <nurv> hi there
12:02:03 GMT <nurv> has been any change from version 2.8 to version 3.0 that caused redis.conf from not being able to be open? I keep getting Permission Denied on it
16:42:50 GMT <winem_> hi. is there any chance to change the suggested cluster configuration provided by redis-trib.rb
16:42:52 GMT <winem_> ?
16:45:21 GMT <winem_> ah, got it. it's enough to change the order of arguments
19:16:28 GMT <UserOfRedis123> I have a strange problem I'm hoping somebody can help me find a better way to debug. I have some keys that are disappearing, INFO is saying no keys are expunged at all. I'm watching the keys in question with notify-keyspace-events/psubscribe, and only see the SET and EXPIRE commands being ran against them. I have adjusted the TTL to verify EXPIRED works, and is not what is happening, and that I also see a DELs in the psubscribe
19:18:55 GMT <UserOfRedis123> This is on 3.2.4 on elasticache, but I had the exact same problem on 1.8.x. Is there some way I can get info about what happened to a particular key that notify-keyspace-events is not reporting?
19:19:33 GMT <UserOfRedis123> expunged should be "evicted" to get the correct redis terms: evicted_keys:0
19:20:38 GMT <minus> is MONITOR saying anything? is your instance maybe unprotected on the internet?
19:20:56 GMT <minus> that's all i can come up with
19:23:29 GMT <UserOfRedis123> The server is on a private subnet. I have not tried MONITOR yet, as instantaneous_ops_per_sec is over 10,000... I'm concerned MONITOR could cause a problem.
19:27:23 GMT <minus> yeah, that sounds a bit problematic. MONITOR shouldn't cause big problem though, a bit of a slowdown at most. maybe you can set up a slave and experiment on that?
19:33:02 GMT <UserOfRedis123> good enough, I've attached a MONITOR redis-cli and I'm running it through grep for the key name prefix to at least cut the noise down. Hopefully this gives some clues.
20:37:25 GMT <pdpol> anyone around know much about `SCRIPT LOAD`?