- 15 6月, 2012 1 次提交
-
-
由 antirez 提交于
In order to implement reply buffer limits introduced in 2.6 and useful to close the connection under user-selected circumastances of big output buffers (for instance slow consumers in pub/sub, a blocked slave, and so forth) Redis takes a counter with the amount of used memory in objects inside the output list stored into c->reply. The computation was broken in the function setDeferredMultiBulkLength(), in the case the object was glued with the next one. This caused the c->reply_bytes field to go out of sync, be subtracted more than needed, and wrap back near to ULONG_MAX values. This commit fixes this bug and adds an assertion that is able to trap this class of problems. This problem was discovered looking at the INFO output of an unrelated issue (issue #547).
-
- 07 4月, 2012 1 次提交
-
-
由 antirez 提交于
New client info field added to CLIENT LIST output: multi, containing the length of the current pipeline. Test modified accordingly.
-
- 29 3月, 2012 2 次提交
- 27 3月, 2012 1 次提交
-
-
由 Premysl Hruby 提交于
-
- 14 3月, 2012 2 次提交
- 13 3月, 2012 3 次提交
- 07 3月, 2012 1 次提交
-
-
由 antirez 提交于
anetPeerToString() automatically populates ip/port with something that may be provided to the user as output in case of errors.
-
- 16 2月, 2012 1 次提交
-
-
由 antirez 提交于
-
- 08 2月, 2012 1 次提交
-
-
由 antirez 提交于
Fixes to c->reply_bytes computation, and debug messages to closely study the behavior of memory pressure + slaves + maxmemory + blocked slaves.
-
- 07 2月, 2012 1 次提交
-
-
由 antirez 提交于
Precision of getClientOutputBufferMemoryUsage() greatily improved, see issue #327 for more information.
-
- 06 2月, 2012 1 次提交
-
-
由 antirez 提交于
-
- 04 2月, 2012 2 次提交
-
-
由 antirez 提交于
1) sendReplyToClient() now no longer stops transferring data to a single client in the case we are out of memory (maxmemory-wise). 2) in processCommand() the idea of we being out of memory is no longer the naive zmalloc_used_memory() > server.maxmemory. To say if we can accept or not write queries is up to the return value of freeMemoryIfNeeded(), that has full control about that. 3) freeMemoryIfNeeded() now does its math without considering output buffers size. But at the same time it can't let the output buffers to put us too much outside the max memory limit, so at the same time it makes sure there is enough effort into delivering the output buffers to the slaves, calling the write handler directly. This three changes are the result of many tests, I found (partially empirically) that is the best way to address the problem, but maybe we'll find better solutions in the future.
-
由 antirez 提交于
Use less memory when emitting the protocol, by using more shared objects for commonly emitted parts of the protocol.
-
- 26 1月, 2012 1 次提交
-
-
由 antirez 提交于
-
- 24 1月, 2012 5 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
Client output buffer limits: configuration of parameters for the different classes of clients implemented.
-
由 antirez 提交于
asyncCloseClientOnOutputBufferLimitReached() now ignores clients with REDIS_CLOSE_ASAP flag already set. Return value of the function changed from int to void since it is not used. Fixed logging of the client scheduled to be closed.
-
由 antirez 提交于
-
- 23 1月, 2012 1 次提交
-
-
由 antirez 提交于
Implementation of the internals that make possible to terminate clients overcoming configured output buffer (soft and hard) limits.
-
- 17 1月, 2012 2 次提交
- 12 1月, 2012 1 次提交
-
-
由 antirez 提交于
On crash print information about the current client (if any), command vector, and object associated to first argument assuming it is a key.
-
- 31 12月, 2011 2 次提交
-
-
由 antirez 提交于
Protections against protocol desyncs, leading to infinite query buffer growing, due to nul-terms in specific bytes of the request or indefinitely long multi bulk or bulk count strings without newlines. This bug is related to Issue #141 as well.
-
由 antirez 提交于
Fixed replication when multiple slaves are attaching at the same time. The output buffer was not copied correctly between slaves. This fixes issue #141.
-
- 21 12月, 2011 1 次提交
-
-
由 antirez 提交于
-
- 19 12月, 2011 1 次提交
-
-
由 antirez 提交于
Fixed memleak in CLIENT INFO, added simple test that will work as regression test on mac os x and in the CI when running over valgrind. This fixes issue #256
-
- 28 11月, 2011 1 次提交
-
-
由 antirez 提交于
-
- 25 11月, 2011 1 次提交
-
-
由 antirez 提交于
-
- 24 11月, 2011 3 次提交
-
-
由 antirez 提交于
minor refactoring to networking.c adding a separated function to get a string representing the current state of all the connected clients.
-
由 antirez 提交于
-
由 antirez 提交于
new counter in INFO output: rejected_connections with number of dropped connections because of maxclients limit reached.
-
- 21 11月, 2011 4 次提交