- 27 Sep, 2019 4 commits
-
-
antirez authored
-
antirez authored
We don't want that the API could be used directly in an unsafe way, without checking if there is an active child. Now the safety checks are moved directly in the function performing the operations.
-
antirez authored
-
antirez authored
We can't expect SIGUSR1 to have any specific value range, so let's define an exit code that we can handle in a special way. This also fixes an #include <wait.h> that is not standard.
-
- 02 Sep, 2019 1 commit
-
-
antirez authored
-
- 25 Aug, 2019 1 commit
-
-
Oran Agra authored
-
- 05 Aug, 2019 1 commit
-
-
antirez authored
-
- 30 Jul, 2019 1 commit
-
-
Oran Agra authored
-
- 24 Jul, 2019 1 commit
-
-
antirez authored
-
- 23 Jul, 2019 3 commits
-
-
antirez authored
-
antirez authored
-
Madelyn Olson authored
-
- 22 Jul, 2019 2 commits
- 21 Jul, 2019 1 commit
-
-
Oran Agra authored
This is especially needed in diskless loading, were a short read could have caused redis to exit. now the module can handle the error and return to the caller gracefully. this fixes #5326
-
- 17 Jul, 2019 2 commits
-
-
Oran Agra authored
* create module API for forking child processes. * refactor duplicate code around creating and tracking forks by AOF and RDB. * child processes listen to SIGUSR1 and dies exitFromChild in order to eliminate a valgrind warning of unhandled signal. * note that BGSAVE error reply has changed. valgrind error is: Process terminating with default action of signal 10 (SIGUSR1)
-
zhaozhao.zz authored
-
- 08 Jul, 2019 2 commits
-
-
Oran Agra authored
The implementation of the diskless replication was currently diskless only on the master side. The slave side was still storing the received rdb file to the disk before loading it back in and parsing it. This commit adds two modes to load rdb directly from socket: 1) when-empty 2) using "swapdb" the third mode of using diskless slave by flushdb is risky and currently not included. other changes: -------------- distinguish between aof configuration and state so that we can re-enable aof only when sync eventually succeeds (and not when exiting from readSyncBulkPayload after a failed attempt) also a CONFIG GET and INFO during rdb loading would have lied When loading rdb from the network, don't kill the server on short read (that can be a network error) Fix rdb check when performed on preamble AOF tests: run replication tests for diskless slave too make replication test a bit more aggressive Add test for diskless load swapdb
-
Angus Pearson authored
-
- 05 Jul, 2019 1 commit
-
-
antirez authored
-
- 03 Jul, 2019 2 commits
- 30 Jun, 2019 2 commits
- 13 Jun, 2019 1 commit
-
-
Angus Pearson authored
-
- 10 Jun, 2019 1 commit
-
-
Angus Pearson authored
and to keep OBJ_* enum to string canonicalization in one place.
-
- 06 May, 2019 7 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
Ubuntu authored
Now threads are stopped even when the connections drop immediately to zero, not allowing the networking code to detect the condition and stop the threads. serverCron() will handle that.
-
antirez authored
This is just an experiment for now, there are a couple of race conditions, mostly harmless for the performance gain experiment that this commit represents so far. The general idea here is to take Redis single threaded and instead fan-out on expansive kernel calls: write(2) in this case, but the same concept could be easily implemented for read(2) and protcol parsing. However just threading writes like in this commit, is enough to evaluate if the approach is sounding.
-
- 29 Apr, 2019 1 commit
-
-
zhaozhao.zz authored
-
- 16 Apr, 2019 1 commit
-
-
Itamar Haber authored
Fixes #6012. As long as "INFO is broken", this should be adequate IMO. Once we rework `INFO`, perhaps into RESP3, this implementation should be revisited.
-
- 24 Mar, 2019 1 commit
-
-
Oran Agra authored
when redis appends the blocked client reply list to the real client, it didn't bother to check if it is in fact the master client. so a slave executing that module command will send replies to the master, causing the master to send the slave error responses, which will mess up the replication offset (slave will advance it's replication offset, and the master does not)
-
- 21 Mar, 2019 2 commits
- 18 Mar, 2019 1 commit
-
-
Yossi Gottlieb authored
-
- 15 Mar, 2019 1 commit
-
-
Yossi Gottlieb authored
-