- 16 2月, 2018 6 次提交
-
-
由 Dvir Volk 提交于
-
由 Dvir Volk 提交于
-
由 Dvir Volk 提交于
-
由 Dvir Volk 提交于
-
由 antirez 提交于
See #3832.
-
由 oranagra 提交于
since slave isn't replying to it's master, these errors go unnoticed. since we don't expect the master to send garbadge to the slave, this should be safe. (as long as we don't log OOM errors there)
-
- 13 2月, 2018 5 次提交
-
-
由 charsyam 提交于
-
由 Guy Benoish 提交于
-
由 antirez 提交于
See #3858.
-
由 Guy Benoish 提交于
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).
-
由 Oran Agra 提交于
in some cases LATENCY HISTORY reported latency that was higher than the max latency reported by LATENCY LATEST / DOCTOR
-
- 03 2月, 2018 1 次提交
-
-
由 antirez 提交于
-
- 02 2月, 2018 1 次提交
-
-
由 antirez 提交于
-
- 24 1月, 2018 5 次提交
-
-
由 antirez 提交于
-
由 jianqingdu 提交于
fix not call va_end when syncWrite() failed in sendSynchronousCommand()
-
由 Yusaku Kaneta 提交于
-
由 Mark Nunberg 提交于
Older versions might not have this function.
-
由 antirez 提交于
-
- 18 1月, 2018 21 次提交
-
-
由 antirez 提交于
-
由 Guy Benoish 提交于
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 提交于
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.
-
由 antirez 提交于
The behavior is well specified by the code itself.
-
由 heqin 提交于
-
由 antirez 提交于
-
由 qinchao 提交于
, see issue: https://github.com/antirez/redis/issues/4587
-
由 Oran Agra 提交于
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.
-
由 zhaozhao.zz 提交于
-
由 antirez 提交于
-
由 zhaozhao.zz 提交于
-
由 antirez 提交于
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.
-
由 antirez 提交于
-
由 antirez 提交于
We already had client buffer limits exported as configuration options. Stick with the naming scheme already used. See #4568.
-
由 antirez 提交于
Related to #4568.
-
由 gnuhpc 提交于
-
由 Dvir Volk 提交于
-
由 zhaozhao.zz 提交于
-
由 Oran Agra 提交于
-
由 Oran Agra 提交于
- protocol parsing (processMultibulkBuffer) was limitted to 32big positions in the buffer readQueryFromClient potential overflow - rioWriteBulkCount used int, although rioWriteBulkString gave it size_t - several places in sds.c that used int for string length or index. - bugfix in RM_SaveAuxField (return was 1 or -1 and not length) - RM_SaveStringBuffer was limitted to 32bit length
-
由 heqin 提交于
-
- 10 1月, 2018 1 次提交
-
-
由 antirez 提交于
This is a fix for the #3819 improvements. The o->ptr may change because of hllSparseSet() calls, so 'hdr' must be correctly re-fetched.
-