- 12 Mar, 2018 2 commits
-
-
Oran Agra authored
other fixes / improvements: - LUA script memory isn't taken from zmalloc (taken from libc malloc) so it can cause high fragmentation ratio to be displayed (which is false) - there was a problem with "fragmentation" info being calculated from RSS and used_memory sampled at different times (now sampling them together) other details: - adding a few more allocator info fields to INFO and MEMORY commands - improve defrag test to measure defrag latency of big keys - increasing the accuracy of the defrag test (by looking at real grag info) this way we can use an even lower threshold and still avoid false positives - keep the old (total) "fragmentation" field unchanged, but add new ones for spcific things - add these the MEMORY DOCTOR command - deduct LUA memory from the rss in case of non jemalloc allocator (one for which we don't "allocator active/used") - reduce sampling rate of the rss and allocator info
-
Oran Agra authored
- big keys are not defragged in one go from within the dict scan instead they are scanned in parts after the main dict hash bucket is done. - add latency monitor sample for defrag - change default active-defrag-cycle-min to induce lower latency - make active defrag start a new scan right away if needed, so it's easier (for the test suite) to detect when it's done - make active defrag quick the current cycle after each db / big key - defrag some non key long term global allocations - some refactoring for smaller functions and more reusable code - during dict rehashing, one scan iteration of the dict, can end up scanning one bucket in the smaller dict and many many buckets in the larger dict. so waiting for 16 scan iterations before checking the time, may be much too long.
-
- 15 Feb, 2018 3 commits
-
-
antirez authored
-
Salvatore Sanfilippo authored
Keyspace notifications API for modules
-
antirez authored
-
- 14 Feb, 2018 10 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.
-