1. mirror
  2. redis

Commits

Author Commit Message Date Builds
antirez
Differentiate SCRIPT KILL error replies. When calling SCRIPT KILL currently you can get two errors: * No script in timeout (busy) state. * The script already performed a write. It is useful to be able to distinguish the two errors, but right now both start with "ERR" prefix, so string matching (that is fragile) must be used. This commit introduces two different prefixes. -NOTBUSY and -UNKILLABLE respectively to reply with an error wh…
NanXiao
Update src/redis-benchmark.c The code of current implementation: if (c->pending == 0) clientDone(c); In clientDone function, the c's memory has been freed, then the loop will continue: while(c->pending). The memory of c has been freed now, so c->pending is invalid (c is an invalid pointer now), and this will cause memory dump in some platforams(eg: Solaris). So I think the code should be modified as: if (c->pending == 0) { …
bitbucket
Merge branch 'unstable' of https://github.com/antirez/redis into unstable
antirez
Fix MULTI / EXEC rendering in MONITOR output. Before of this commit it used to be like this: MULTI EXEC ... actual commands of the transaction ... Because after all that is the natural order of things. Transaction commands are queued and executed *only after* EXEC is called. However this makes debugging with MONITOR a mess, so the code was modified to provide a coherent output. What happens is that MULTI is rendered in the MONITOR output …
antirez
Fix MULTI / EXEC rendering in MONITOR output. Before of this commit it used to be like this: MULTI EXEC ... actual commands of the transaction ... Because after all that is the natural order of things. Transaction commands are queued and executed *only after* EXEC is called. However this makes debugging with MONITOR a mess, so the code was modified to provide a coherent output. What happens is that MULTI is rendered in the MONITOR output …
bitbucket
Merge branch 'unstable' of https://github.com/antirez/redis into unstable
antirez
Merge remote-tracking branch 'origin/2.6' into 2.6
antirez
Allow AUTH when Redis is busy because of timedout Lua script. If the server is password protected we need to accept AUTH when there is a server busy (-BUSY) condition, otherwise it will be impossible to send SHUTDOWN NOSAVE or SCRIPT KILL. This fixes issue #708.
antirez
Allow AUTH when Redis is busy because of timedout Lua script. If the server is password protected we need to accept AUTH when there is a server busy (-BUSY) condition, otherwise it will be impossible to send SHUTDOWN NOSAVE or SCRIPT KILL. This fixes issue #708.
bitbucket
Merge branch 'unstable' of https://github.com/antirez/redis into unstable
Salvatore Sanfilippo
Merge pull request #707 from NanXiao/patch-1 Update src/redis-benchmark.c
NanXiao
Update src/redis-benchmark.c The code of current implementation: if (c->pending == 0) clientDone(c); In clientDone function, the c's memory has been freed, then the loop will continue: while(c->pending). The memory of c has been freed now, so c->pending is invalid (c is an invalid pointer now), and this will cause memory dump in some platforams(eg: Solaris). So I think the code should be modified as: if (c->pending ==…
bitbucket
Merge branch 'unstable' of https://github.com/antirez/redis into unstable
antirez
CONTRIBUTING file updated.
antirez
CONTRIBUTING file updated.
antirez
Redis 2.6.0 RC8 (2.5.14)
Tags
2.6.0-rc8
bitbucket
Merge branch 'unstable' of https://github.com/antirez/redis into unstable
dvir volk
fixed server install script to rewrite the default configuration file and not a template, and removed the old config template Conflicts: utils/redis.conf.tpl
Salvatore Sanfilippo
Merge pull request #544 from dvirsky/2.6 fixed install script to rewrite the default config
bitbucket
Merge branch 'unstable' of https://github.com/antirez/redis into unstable
antirez
Hash function switched to murmurhash2. The previously used hash function, djbhash, is not secure against collision attacks even when the seed is randomized as there are simple ways to find seed-independent collisions. The new hash function appears to be safe (or much harder to exploit at least) in this case, and has better distribution. Better distribution does not always means that's better. For instance in a fast benchmark with "DE…
antirez
Hash function switched to murmurhash2. The previously used hash function, djbhash, is not secure against collision attacks even when the seed is randomized as there are simple ways to find seed-independent collisions. The new hash function appears to be safe (or much harder to exploit at least) in this case, and has better distribution. Better distribution does not always means that's better. For instance in a fast benchmark with "DE…
antirez
Warn when configured maxmemory value seems odd. This commit warns the user with a log at "warning" level if: 1) After the server startup the maxmemory limit was found to be < 1MB. 2) After a CONFIG SET command modifying the maxmemory setting the limit is set to a value that is smaller than the currently used memory. The behaviour of the Redis server is unmodified, and this wil not make the CONFIG SET command or a wrong configuration in redis.…
antirez
Warn when configured maxmemory value seems odd. This commit warns the user with a log at "warning" level if: 1) After the server startup the maxmemory limit was found to be < 1MB. 2) After a CONFIG SET command modifying the maxmemory setting the limit is set to a value that is smaller than the currently used memory. The behaviour of the Redis server is unmodified, and this wil not make the CONFIG SET command or a wrong configuration in redis.…
antirez
Warn when configured maxmemory value seems odd. This commit warns the user with a log at "warning" level if: 1) After the server startup the maxmemory limit was found to be < 1MB. 2) After a CONFIG SET command modifying the maxmemory setting the limit is set to a value that is smaller than the currently used memory. The behaviour of the Redis server is unmodified, and this wil not make the CONFIG SET command or a wrong configuration in redis.…
antirez
Include time.h in ae.c as we now use time().
antirez
Include time.h in ae.c as we now use time().
Jokea
Force expire all timer events when system clock skew is detected. When system time changes back, the timer will not worker properly hence some core functionality of redis will stop working(e.g. replication, bgsave, etc). See issue #633 for details. The patch saves the previous time and when a system clock skew is detected, it will force expire all timers. Modiifed by @antirez: the previous time was moved into the eventLoop structure to make sure the library is…
Jokea
Force expire all timer events when system clock skew is detected. When system time changes back, the timer will not worker properly hence some core functionality of redis will stop working(e.g. replication, bgsave, etc). See issue #633 for details. The patch saves the previous time and when a system clock skew is detected, it will force expire all timers. Modiifed by @antirez: the previous time was moved into the eventLoop structure to make sure the library is…
antirez
"Timeout receiving bulk data" error message modified. The new message now contains an hint about modifying the repl-timeout configuration directive if the problem persists. This should normally not be needed, because while the master generates the RDB file it makes sure to send newlines to the replication channel to prevent timeouts. However there are times when masters running on very slow systems can completely stop for seconds during the RDB savi…
  1. Prev
  2. Next