- 26 2月, 2012 3 次提交
-
-
由 Jakub Wieczorek 提交于
-
由 Premysl Hruby 提交于
-
由 Premysl Hruby 提交于
-
- 24 2月, 2012 2 次提交
- 23 2月, 2012 5 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 Salvatore Sanfilippo 提交于
Simple install script changes
-
- 22 2月, 2012 9 次提交
-
-
由 antirez 提交于
Fix for issue #306, thanks to tchajed (on github) for the pull request. The original patch was reworked a bit.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
zzlIsInRange() now is capable of handling empty sorted sets that may end inside the data set when loading very old RDB files produced by early-stage versions of Redis.
-
由 Salvatore Sanfilippo 提交于
Force SIGSEGV without HAVE_BACKTRACE (unstable)
-
由 Pieter Noordhuis 提交于
-
由 Pieter Noordhuis 提交于
-
由 antirez 提交于
-
- 21 2月, 2012 1 次提交
-
-
由 antirez 提交于
-
- 20 2月, 2012 3 次提交
- 17 2月, 2012 1 次提交
-
-
由 Pieter Noordhuis 提交于
The cron is responsible for expiring keys. When keys are expired at load time, it is possible that the snapshot of a master node gets modified. This can in turn lead to inconsistencies in the data set. A more concrete example of this behavior follows. A user reported a slave that would show an monotonically increase input buffer length, shortly after completing a SYNC. Also, `INFO` output showed a single blocked client, which could only be the master link. Investigation showed that indeed the `BRPOP` command was fed by the master. This command can only end up in the stream of write operations when it did NOT block, and effectively executed `RPOP`. However, when the key involved in the `BRPOP` is expired BEFORE the command is executed, the client executing it will block. The client in this case, is the master link.
-
- 16 2月, 2012 4 次提交
- 15 2月, 2012 2 次提交
- 14 2月, 2012 6 次提交
- 10 2月, 2012 1 次提交
-
-
由 antirez 提交于
-
- 09 2月, 2012 3 次提交