00:08:47 GMT <cbgbt> :(
00:16:05 GMT <indi_> Hi. I like to see how a redis instances is doing by watching `redis-cli MONITOR`. However, I'm having to grep out all the PINGs from the sentinels. I'm just wondering if this is normal, and if everyone also does this.
14:58:37 GMT <tess_> Hi.I am experience frequent read time out
15:06:36 GMT <tess_> Hi.Facing lots of redis timeout. http://stackoverflow.com/questions/42158495/redistimeouterror-connection-timed-out-error-rails-cache
16:36:43 GMT <ivki> Hello!
16:38:47 GMT <ivki> I iniate to redis from server1 to server2 using /etc/php.d/redis.ini
16:39:28 GMT <ivki> And I often have this error
16:39:30 GMT <ivki> "Uncaught PHP Exception RedisException: "Connection closed""
16:39:41 GMT <ivki> does anyone can help me?
17:01:07 GMT <marcv> Hello. The PTTL command returns the number of milliseconds before a key expires. Is there a command which would return the timestamp at which the key will expire?
17:01:43 GMT <marcv> I cant find it in the doc, so I assume there isn't, but just in case...
17:57:55 GMT <badboy_> no
17:58:00 GMT <badboy_> oh he is gone…
18:57:13 GMT <Pateriack> Im working on something similar to Cyanite (time series metrics database using Cassandra)
18:57:27 GMT <Pateriack> I want to perform aggregations and roll ups on the fly
18:57:48 GMT <Pateriack> I dont have much experience working with/scaling out stateful servers
18:58:05 GMT <Pateriack> somebody recommended keeping aggregations in memory
18:59:02 GMT <Pateriack> im a little worried about how to scale it out.. does that sound like a good use case for redis? I could keep my service stateless and use redis to store aggregations and roll ups as they are computed
19:00:34 GMT <minus> sounds reasonable
19:01:21 GMT <Pateriack> i might be over-engineering/prematurely optimizing things here
19:01:37 GMT <Pateriack> im still not quite sure what sort of load my ingest service will be under
19:04:12 GMT <minus> keeping aggregations in your application's memory does seem more reasonable, but whether that works or not depends on your design i guess
19:05:36 GMT <Pateriack> mmm
19:06:23 GMT <Pateriack> the only thing that i worry about is rehydrating my application if it goes down
19:06:35 GMT <Pateriack> i guess i still have the same issue if redis were to go down
19:07:36 GMT <Pateriack> i think ill start building it under the assumption that ill be keeping aggregations in memory and cross that bridge when i get there
19:07:37 GMT <Pateriack> thanks!
19:08:45 GMT <minus> with redis you could use redis cluster or redis sentinel to minimize the impact
19:11:18 GMT <Pateriack> true