- 14 Feb, 2018 4 commits
- 13 Feb, 2018 9 commits
-
-
Salvatore Sanfilippo authored
Removing duplicated code to set max latency
-
charsyam authored
-
antirez authored
See #3832.
-
Salvatore Sanfilippo authored
when a slave responds with an error on commands that come from master, log it
-
Salvatore Sanfilippo authored
enlarged buffer given to ld2string
-
antirez authored
See #3858.
-
Guy Benoish authored
It is possible to do BGREWRITEAOF even if appendonly=no. This is by design. stopAppendonly() didn't turn off aof_rewrite_scheduled (it can be turned on again by BGREWRITEAOF even while appendonly is off anyway). After configuring `appendonly yes` it will see that the state is AOF_OFF, there's no RDB fork, so it will do rewriteAppendOnlyFileBackground() which will fail since the aof_child_pid is set (was scheduled and started by cron). Solution: stopAppendonly() will turn off the schedule flag (regardless of who asked for it). startAppendonly() will terminate any existing fork and start a new one (so it is the most recent).
-
Salvatore Sanfilippo authored
fix to latency monitor reporting wrong max latency
-
Oran Agra authored
in some cases LATENCY HISTORY reported latency that was higher than the max latency reported by LATENCY LATEST / DOCTOR
-
- 02 Feb, 2018 1 commit
-
-
antirez authored
-
- 24 Jan, 2018 3 commits
-
-
Salvatore Sanfilippo authored
fix not call va_end() when syncWrite() failed
-
Salvatore Sanfilippo authored
redismodule.h: Check ModuleNameBusy before calling it
-
antirez authored
-
- 23 Jan, 2018 1 commit
-
-
Mark Nunberg authored
Older versions might not have this function.
-
- 18 Jan, 2018 3 commits
-
-
antirez authored
-
Guy Benoish authored
When feeding the master with a high rate traffic the the slave's feed is much slower. This causes the replication buffer to grow (indefinitely) which leads to slave disconnection. The problem is that writeToClient() decides to stop writing after NET_MAX_WRITES_PER_EVENT writes (In order to be fair to clients). We should ignore this when the client is a slave. It's better if clients wait longer, the alternative is that the slave has no chance to stay in sync in this situation.
-
antirez authored
See #3462 and related PRs. We use a simple algorithm to calculate the level of affinity violation, and then an optimizer that performs random swaps until things improve.
-
- 17 Jan, 2018 4 commits
-
-
antirez authored
The behavior is well specified by the code itself.
-
Salvatore Sanfilippo authored
fixbug for #4545 dead loop aof rewrite
-
heqin authored
-
Salvatore Sanfilippo authored
fix assert problem in ZIP_DECODE_PREVLENSIZE macro
-
- 16 Jan, 2018 4 commits
-
-
antirez authored
-
qinchao authored
, see issue: https://github.com/antirez/redis/issues/4587
-
Salvatore Sanfilippo authored
PSYNC2 fix - promoted slave should hold on to it's backlog
-
Oran Agra authored
after a slave is promoted (assuming it has no slaves and it booted over an hour ago), it will lose it's replication backlog at the next replication cron, rather than waiting for slaves to connect to it. so on a simple master/slave faiover, if the new slave doesn't connect immediately, it may be too later and PSYNC2 will fail.
-
- 15 Jan, 2018 3 commits
-
-
zhaozhao.zz authored
-
antirez authored
-
Salvatore Sanfilippo authored
lazyfree: fix memory leak for lazyfree-lazy-server-del
-
- 14 Jan, 2018 1 commit
-
-
zhaozhao.zz authored
-
- 12 Jan, 2018 5 commits
-
-
Salvatore Sanfilippo authored
redis-benchmark: bugfix - handle zero liveclients in right way
-
Salvatore Sanfilippo authored
Added RM_UnlinkKey - a low level analog to UNLINK command
-
antirez authored
-
Salvatore Sanfilippo authored
Fix a typo(maybe instruction?) in crash log
-
antirez authored
This fixes a crash with Redis Cluster when OBJECT is mis-used, because getKeysUsingCommandTable() will call serverPanic() detecting we are accessing an invalid argument in the case "OBJECT foo" is called. This bug was introduced when OBJECT HELP was introduced, because the key argument is set fixed at index 2 in the command table, however now OBJECT may be called with an insufficient number of arguments to extract the key. The "Right Thing" would be to have a specific function to extract keys from the OBJECT command, however this is kinda of an overkill, so I preferred to make getKeysUsingCommandTable() more robust and just return no keys when it's not possible to honor the command table, because new commands are often added and also there are a number with an HELP subcommand violating the normal form, and crashing for this trivial reason or having many command-specific key extraction functions is not great.
-
- 11 Jan, 2018 2 commits