- 05 7月, 2013 4 次提交
- 03 7月, 2013 2 次提交
-
-
由 antirez 提交于
When in --pipe mode, after all the data transfer to the server is complete, now redis-cli waits at max the specified amount of seconds (30 by default, use 0 to wait forever) without receiving any reply at all from the server. After this time limit the operation is aborted with an error. That's related to issue #681.
-
由 antirez 提交于
If the protocol read from stdin happened to contain grabage (invalid random chars), in the previous implementation it was possible to end with something like: dksfjdksjflskfjl*2\r\n$4\r\nECHO.... That is invalid as the *2 should start into a new line. Now we prefix the ECHO with a CRLF that has no effects on the server but prevents this issues most of the times. Of course if the offending wrong sequence is something like: $3248772349\r\n No one is going to save us as Redis will wait for data in the context of a big argument, so this fix does not cover all the cases. This partially fixes issue #681.
-
- 02 7月, 2013 5 次提交
-
-
由 antirez 提交于
It causes catastrophic performance for certain inputs. Relevant NetBSD commit: http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libc/stdlib/qsort.c?rev=1.20&content-type=text/x-cvsweb-markup&only_with_tag=MAIN This fixes issue #968.
-
由 Salvatore Sanfilippo 提交于
fix randstring bug in ziplist.c
-
由 antirez 提交于
This fixes issue #1094.
-
由 antirez 提交于
The function is used to test that the specified string looks like just as the basename of a path, without any absolute or relative path.
-
由 antirez 提交于
-
- 28 6月, 2013 2 次提交
- 27 6月, 2013 1 次提交
-
-
由 antirez 提交于
-
- 26 6月, 2013 3 次提交
-
-
由 antirez 提交于
-
由 Salvatore Sanfilippo 提交于
netbsd support
-
由 antirez 提交于
Clients using SYNC to replicate are older implementations, such as redis-cli --slave, and are not designed to acknowledge the master with REPLCONF ACK commands, so we don't have any feedback and should not disconnect them on timeout.
-
- 25 6月, 2013 9 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
It should be called just one time at startup and not every time the Lua scripting engine is re-initialized, otherwise memory is leaked.
-
由 antirez 提交于
This commit uses the Replication Script Cache in order to avoid translating EVALSHA into EVAL whenever possible for both the AOF and slaves.
-
- 24 6月, 2013 1 次提交
-
-
由 antirez 提交于
This code is only responsible to take an LRU-evicted fixed length cache of SHA1 that we are sure all the slaves received. In this commit only the implementation is provided, but the Redis core does not use it to actually send EVALSHA to slaves when possible.
-
- 21 6月, 2013 1 次提交
-
-
由 antirez 提交于
The old REDIS_CMD_FORCE_REPLICATION flag was removed from the implementation of Redis, now there is a new API to force specific executions of a command to be propagated to AOF / Replication link: void forceCommandPropagation(int flags); The new API is also compatible with Lua scripting, so a script that will execute commands that are forced to be propagated, will also be propagated itself accordingly even if no change to data is operated. As a side effect, this new design fixes the issue with scripts not able to propagate PUBLISH to slaves (issue #873).
-
- 20 6月, 2013 8 次提交
-
-
由 Salvatore Sanfilippo 提交于
Initialize char* to NULL to remove compiler warning
-
由 Jan-Erik Rediger 提交于
-
由 antirez 提交于
The result is an empty list but it is handy to call it programmatically.
-
由 antirez 提交于
Currently it implements three subcommands: PUBSUB CHANNELS [<pattern>] List channels with non-zero subscribers. PUBSUB NUMSUB [channel_1 ...] List number of subscribers for channels. PUBSUB NUMPAT Return number of subscribed patterns.
-
由 antirez 提交于
Sentinel was not able to detect slaves when connected to a very recent version of Redis master since a previos non-backward compatible change to INFO broken the parsing of the slaves ip:port INFO output. This fixes issue #1164
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
This fixes issue #1163
-
- 19 6月, 2013 2 次提交
-
-
由 antirez 提交于
When the semantics changed from logfile = NULL to logfile = "" to log into standard output, no proper change was made to logStackTrace() to make it able to work with the new setup. This commit fixes the issue.
-
由 antirez 提交于
lua_pcall error handler now formats errors in a way more similar to luaPushError() so that errors generated in different contexts look alike.
-
- 18 6月, 2013 1 次提交
-
-
由 antirez 提交于
When calling Lua scripts we try to report not just the error but information about the code line causing the error.
-
- 17 6月, 2013 1 次提交
-
-
由 Salvatore Sanfilippo 提交于
Try to report source of bad Lua API calls
-