- 02 4月, 2013 2 次提交
-
-
由 antirez 提交于
-
由 Salvatore Sanfilippo 提交于
Build improvements
-
- 29 3月, 2013 1 次提交
-
-
由 charsyam 提交于
-
- 28 3月, 2013 7 次提交
- 27 3月, 2013 4 次提交
- 26 3月, 2013 7 次提交
-
-
由 antirez 提交于
Fixes issue #1024.
-
由 antirez 提交于
This commit fixes two corner cases for the TTL command. 1) When the key was already logically expired (expire time older than current time) the command returned -1 instead of -2. 2) When the key was existing and the expire was found to be exactly 0 (the key was just about to expire), the command reported -1 (that is, no expire) instead of a TTL of zero (that is, about to expire).
-
由 antirez 提交于
-
由 antirez 提交于
MULTI/EXEC is now propagated to the AOF / Slaves only once we encounter the first command that is not a read-only one inside the transaction. The old behavior was to always propagate an empty MULTI/EXEC block when the transaction was composed just of read only commands, or even completely empty. This created two problems: 1) It's a bandwidth waste in the replication link and a space waste inside the AOF file. 2) We used to always increment server.dirty to force the propagation of the EXEC command, resulting into triggering RDB saves more often than needed. Note: even read-only commands may also trigger writes that will be propagated, when we access a key that is found expired and Redis will synthesize a DEL operation. However there is no need for this to stay inside the transaction itself, but only to be ordered. So for instance something like: MULTI GET foo SET key zap EXEC May be propagated into: DEL foo MULTI SET key zap EXEC While the DEL is outside the transaction, the commands are delivered in the right order and it is not possible for other commands to be inserted between DEL and MULTI.
-
由 antirez 提交于
-
由 antirez 提交于
The behavior is the same, but the code is now cleaner and uses the proper interface instead of dealing directly with AOF/replication functions.
-
由 Salvatore Sanfilippo 提交于
Update config.c
-
- 25 3月, 2013 6 次提交
- 23 3月, 2013 2 次提交
-
-
由 antirez 提交于
Redis-tools is a connection of tools no longer mantained that was intented as a way to economically make sense of Redis in the pre-vmware sponsorship era. However there was a nice redis-stat utility, this commit imports one of the functionalities of this tool here in redis-cli as it seems to be pretty useful. Usage: redis-cli --stat The output is similar to vmstat in the format, but with Redis specific stuff of course. From the point of view of the monitored instance, only INFO is used in order to grab data.
-
由 antirez 提交于
This is needed in order to colorize it as next step. We use conventions in output messages such as >>> This is an action *** This is a warning [ERR] This is an error [OK] That's fine And so forth, so that a color will be associated checking the first three chars.
-
- 22 3月, 2013 9 次提交
-
-
由 antirez 提交于
Slot zero was hardcoded (!)
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
This way we are sure to destroy the slot->key map every time we destroy the DB, for instance when reloading a DB due to replication.
-
由 antirez 提交于
Open slots are slots found in importing or migrating slot when a cluster check is performed.
-
- 21 3月, 2013 2 次提交