- 13 Feb, 2020 1 commit
-
-
antirez authored
-
- 12 Feb, 2020 1 commit
-
-
antirez authored
-
- 11 Feb, 2020 2 commits
- 10 Feb, 2020 2 commits
- 07 Feb, 2020 4 commits
- 06 Feb, 2020 14 commits
-
-
Guy Benoish authored
1. Call emptyDb even in case of diskless-load: We want modules to get the same FLUSHDB event as disk-based replication. 2. Do not fire any module events when flushing the backups array. 3. Delete redundant call to signalFlushedDb (Called from emptyDb).
-
Guy Benoish authored
-
Oran Agra authored
-
Guy Benoish authored
1. server.repl_no_slaves_since can be set when a MONITOR client disconnects 2. c->repl_ack_time can be set by a newline from a MONITOR client 3. Improved comments
-
Oran Agra authored
-
Oran Agra authored
althouh in theory, users can do BGREWRITEAOF even if aof is disabled, i suppose it is more common that the scheduled flag is set by either startAppendOnly, of a failed initial AOFRW fork (AOF_WAIT_REWRITE)
-
Oran Agra authored
replicationUnsetMaster can be called from other places, not just replicaofCOmmand, and all of these need to restart AOF
-
Oran Agra authored
-
Oran Agra authored
this function possibly iterates on the module list
-
Oran Agra authored
using panic rather than exit means you get s stack trace of the code path that experianced the error, and possibly other info.
-
Oran Agra authored
currently there's no bug since the flags these functions handle are always lower than 32bit, but still better fix the type to prevent future bugs.
-
Oran Agra authored
the warning condition was if usage > limit (saying it'll cause eviction or oom), but in fact the eviction and oom depends on used minus slave buffers. other than fixing the condition, i add info about the current usage and limit, which may be useful when looking at the log.
-
Oran Agra authored
-
Oran Agra authored
SELECT, and HELLO are commands that may be executed by the client as soon as it connects, there's no reason to block them, preventing the client from doing the rest of his sequence (which might just be INFO or CONFIG, etc). MONITOR, DEBUG, SLOWLOG, TIME, LASTSAVE are all non-data accessing commands, which there's no reason to block.
-
- 05 Feb, 2020 4 commits
-
-
Oran Agra authored
-
Oran Agra authored
-
Oran Agra authored
We noticed that the error replies for the generic mechanism for enums are very verbose for config file parsing, but not for config set command. instead of replicating this code, i did a small refactoring to share code between CONFIG SET and config file parsing. and also renamed the enum group functions to be consistent with the naming of other types.
-
Oran Agra authored
-
- 04 Feb, 2020 4 commits
- 03 Feb, 2020 2 commits
-
-
Oran Agra authored
-
Guy Benoish authored
Because "keymiss" is "special" compared to the rest of the notifications (Trying not to break existing apps using the 'A' format for notifications) Also updated redis.conf and module.c docs
-
- 02 Feb, 2020 1 commit
-
-
Leo Murillo authored
-
- 30 Jan, 2020 2 commits
-
-
Guy Benoish authored
This bug affected RM_StringToLongDouble and HINCRBYFLOAT. I added tests for both cases. Main changes: 1. Fixed string2ld to fail if string contains \0 in the middle 2. Use string2ld in getLongDoubleFromObject - No point of having duplicated code here The two changes above broke RM_SaveLongDouble/RM_LoadLongDouble because the long double string was saved with length+1 (An innocent mistake, but it's actually a bug - The length passed to RM_SaveLongDouble should not include the last \0).
-
antirez authored
-
- 29 Jan, 2020 3 commits
-
-
Yossi Gottlieb authored
-
antirez authored
-
antirez authored
-