- 10 Mar, 2012 3 commits
-
-
antirez authored
Minor code aesthetic change to use Redis code base style rule of saving vertical space when possible.
-
antirez authored
Removed handling of deprecated hash-max-zipmap-entries nad hash-map-zipmap-value. Pieter is too good with users ;). Better to have them switch to a saner configuration ASAP after the 2.6 upgrade.
-
antirez authored
Added a top-function comment to rioWriteHashIteratorCursor() to better specify what the function does. Not immediately clear from the name.
-
- 08 Mar, 2012 4 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
The Run ID is a field that identifies a single execution of the Redis server. It can be useful for many purposes as it makes easy to detect if the instance we are talking about is the same, or if it is a different one or was rebooted. An application of run_id will be in the partial synchronization of replication, where a slave may request a partial sync from a given offset only if it is talking with the same master. Another application is in failover and monitoring scripts.
-
antirez authored
clusterGetRandomName() generalized into getRandomHexChars() so that we can use it for the run_id field as well.
-
- 07 Mar, 2012 5 commits
-
-
antirez authored
By default Redis refuses writes with an error if the latest BGSAVE failed (and at least one save point is configured). However people having good monitoring systems may prefer a server that continues to work, since they are notified that there are problems by their monitoring systems. This commit implements the ability to turn the feature on or off via redis.conf and CONFIG SET.
-
antirez authored
Redis now refuses accepting write queries if RDB persistence is configured, but RDB snapshots can't be generated for some reason. The status of the latest background save operation is now exposed in the INFO output as well. This fixes issue #90.
-
antirez authored
Better MONITOR output, now includes client ip:port or the lua string if the command was executed by the scripting engine.
-
antirez authored
anetPeerToString() automatically populates ip/port with something that may be provided to the user as output in case of errors.
-
antirez authored
-
- 29 Feb, 2012 5 commits
- 28 Feb, 2012 6 commits
-
-
antirez authored
-
antirez authored
The new code uses a more generic data structure to describe redis operations. The new design allows for multiple alsoPropagate() calls within the scope of a single command, that is useful in different contexts. For instance there when there are multiple clients doing BRPOPLPUSH against the same list, and a variadic LPUSH is performed against this list, the blocked clients will both be served, and we should correctly replicate multiple LPUSH commands after the replication of the current command.
-
antirez authored
Added a new API to replicate an additional command after the replication of the currently executed command, in order to propagte the LPUSH originating from RPOPLPUSH and indirectly by BRPOPLPUSH.
-
antirez authored
-
antirez authored
-
antirez authored
-
- 26 Feb, 2012 3 commits
-
-
Jakub Wieczorek authored
-
Premysl Hruby authored
-
Premysl Hruby authored
-
- 24 Feb, 2012 1 commit
-
-
antirez authored
-
- 23 Feb, 2012 2 commits
- 22 Feb, 2012 4 commits
-
-
antirez authored
-
antirez authored
Fix for issue #306, thanks to tchajed (on github) for the pull request. The original patch was reworked a bit.
-
antirez authored
-
antirez authored
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.
-
- 21 Feb, 2012 4 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
antirez authored
-
antirez authored
-
- 19 Feb, 2012 1 commit
-
-
antirez authored
-
- 16 Feb, 2012 2 commits
-
-
Pieter Noordhuis authored
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.
-
antirez authored
-