- 11 4月, 2013 2 次提交
-
-
由 antirez 提交于
Previously redis-cli never tried to raise an error when an unrecognized switch was encountered, as everything after the initial options is to be transmitted to the server. However this is too liberal, as there are no commands starting with "-". So the new behavior is to produce an error if there is an unrecognized switch starting with "-". This should not break past redis-cli usages but should prevent broken options to be silently discarded. As far the first token not starting with "-" is encountered, all the rest is considered to be part of the command, so you cna still use strings starting with "-" as values, like in: redis-cli --port 6380 set foo --my-value
-
由 antirez 提交于
-
- 04 4月, 2013 1 次提交
-
-
由 antirez 提交于
-
- 03 4月, 2013 1 次提交
-
-
由 antirez 提交于
-
- 02 4月, 2013 9 次提交
-
-
由 antirez 提交于
When a BGSAVE fails, Redis used to flood itself trying to BGSAVE at every next cron call, that is either 10 or 100 times per second depending on configuration and server version. This commit does not allow a new automatic BGSAVE attempt to be performed before a few seconds delay (currently 5). This avoids both the auto-flood problem and filling the disk with logs at a serious rate. The five seconds limit, considering a log entry of 200 bytes, will use less than 4 MB of disk space per day that is reasonable, the sysadmin should notice before of catastrofic events especially since by default Redis will stop serving write queries after the first failed BGSAVE. This fixes issue #849
-
由 Johan Bergström 提交于
-
由 Johan Bergström 提交于
-
由 Johan Bergström 提交于
-
由 Johan Bergström 提交于
-
由 Johan Bergström 提交于
-
由 Johan Bergström 提交于
-
由 Johan Bergström 提交于
-
由 Johan Bergström 提交于
This way, we can avoid -rdynamic and -pthread warnings on darwin.
-
- 29 3月, 2013 1 次提交
-
-
由 charsyam 提交于
-
- 28 3月, 2013 7 次提交
- 27 3月, 2013 3 次提交
- 26 3月, 2013 7 次提交
-
-
由 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.
-
由 antirez 提交于
Fixes issue #1024.
-
由 一个手艺人 提交于
Fix bug in configGetCommand function: get correct masterauth value.
-
- 25 3月, 2013 2 次提交
-
-
由 antirez 提交于
Fixes #621.
-
由 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.
-
- 13 3月, 2013 7 次提交
-
-
由 antirez 提交于
server.repl_down_since used to be initialized to the current time at startup. This is wrong since the replication never started. Clients testing this filed to check if data is uptodate should never believe data is recent if we never ever connected to our master.
-
由 antirez 提交于
-
由 antirez 提交于
A test for issue #1001 is included.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 Damian Janowski 提交于
This fixes cases where the RDB file does exist but can't be accessed for any reason. For instance, when the Redis process doesn't have enough permissions on the file.
-
由 antirez 提交于
It was placed for error in initServer() that's called after the configuation is already loaded, causing issue #1000.
-