05:48:44 GMT <snappy> what is RDB/AOF persistence?
08:34:55 GMT <odigem> hi
16:31:30 GMT <snappy> is there a channel for talking about redis code? i'm wondering if either jemalloc/zmalloc align returned allocations
16:34:24 GMT <snappy> oh i see, you cannot assume this because it may use libc malloc
19:05:57 GMT <Brad_> hi
19:06:56 GMT <Brad_> We're seeing errors/warnings like this in our redis log: [7562] 22 Nov 16:03:10.034 # Client addr=10.90.11.50:65107 fd=20 name=Server5 age=18937 idle=210 flags=N db=0 sub=1 psub=2 multi=-1 qbuf=0 qbuf-free=0 obl=16354 oll=416 omem=11682048 events=rw cmd=unsubscribe scheduled to be closed ASAP for overcoming of output buffer limits.
19:07:08 GMT <Brad_> what would that mean and should we be concerned about it?
19:08:11 GMT <Brad_> Seems like we're triggering some sort of limit: http://redis.io/topics/clients#output-buffers-limits Reading the above documentation indicates that normal clients have a default limit of 0, that means, no limit at all. Pub/Sub clients have a default hard limit of 32 megabytes and a soft limit of 8 megabytes per 60 seconds.
19:08:45 GMT <Brad_> I believe we use some normal clients and some pub/sub but not anywhere near these limits so I'm not sure why we're getting this error. How can I troubleshoot this more?
20:27:55 GMT <kryss> Hello guys, maybe we're just morons, but it looks like we're the only Redis user's in the whole internet which have issue like this - can't find anything @google. We have redis instance which seems to be not overloaded, and reports no issues in stats, however on application side we have multiple errors "110 connection time out" when connecting to Redis
20:31:03 GMT <kryss> Redis is on dedicated node - there's no other services running there, with 1Gb connection, and four times more memory than database size. Both redis and kernel are fairly optimised, load is low
20:33:15 GMT <Habbie> last time i had connection time outs it was a bug in the client lib i used
20:33:20 GMT <Habbie> that sent incomplete commands
20:33:23 GMT <Habbie> to which redis of course does not respond
20:33:29 GMT <Habbie> try to rule that out as a reason
20:37:10 GMT <kryss> cool, thanks Habbie, we have not checked on the client side at all, maybe that's the way to go
20:37:16 GMT <Habbie> what client is it?
20:41:20 GMT <kryss> predis for php
20:50:28 GMT <Habbie> ok, don't know that one
20:50:56 GMT <Habbie> kryss, for reference, https://github.com/nrk/redis-lua/issues/49
20:52:52 GMT <kryss> Thanks!