- 27 Sep, 2019 6 commits
-
-
antirez authored
-
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
In theory currently there is only one active child, but the API may change or for bugs in the implementation we may have several (it was like that for years because of a bug). Better to wait for a specific pid and avoid consuing other pending children information.
-
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.
-
- 26 Sep, 2019 1 commit
-
-
antirez authored
Related to #6024.
-
- 05 Sep, 2019 1 commit
-
-
Doug Nelson authored
-
- 25 Aug, 2019 1 commit
-
-
Oran Agra authored
-
- 07 Aug, 2019 1 commit
-
-
Oran Agra authored
-
- 30 Jul, 2019 1 commit
-
-
Oran Agra authored
-
- 22 Jul, 2019 1 commit
-
-
Oran Agra authored
Other changes: * fix memory leak in error handling of rdb loading of type OBJ_MODULE
-
- 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)
-
Oran Agra authored
for instance detached thread safe contexts, or various callbacks that don't provide a context.
-
- 12 Jun, 2019 1 commit
-
-
swilly22 authored
-
- 05 May, 2019 1 commit
-
-
Yossi Gottlieb authored
-
- 16 Apr, 2019 3 commits
-
-
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.
-
Itamar Haber authored
Signed-off-by:
Itamar Haber <itamar@redislabs.com>
-
Itamar Haber authored
Signed-off-by:
Itamar Haber <itamar@redislabs.com>
-
- 10 Apr, 2019 1 commit
-
-
antirez authored
-
- 24 Mar, 2019 2 commits
-
-
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)
-
Yossi Gottlieb authored
-
- 21 Mar, 2019 3 commits
-
-
Yossi Gottlieb authored
Add a flag to automatically protect filters from being called recursively by their own module.
-
Yossi Gottlieb authored
-
Yossi Gottlieb authored
A filter handle is returned and can be used to unregister a filter. In the future it can also be used to further configure or manipulate the filter. Filters are now automatically unregistered when a module unloads.
-
- 19 Mar, 2019 1 commit
-
-
Yossi Gottlieb authored
-
- 18 Mar, 2019 4 commits
-
-
Yossi Gottlieb authored
-
Yossi Gottlieb authored
-
Yossi Gottlieb authored
-
Yossi Gottlieb authored
-
- 15 Mar, 2019 1 commit
-
-
Yossi Gottlieb authored
-
- 14 Mar, 2019 2 commits
-
-
Yossi Gottlieb authored
-
antirez authored
-
- 13 Mar, 2019 1 commit
-
-
swilly22 authored
-
- 11 Mar, 2019 1 commit
-
-
swilly22 authored
-
- 12 Feb, 2019 1 commit
-
-
Guy Benoish authored
In some cases processMultibulkBuffer uses sdsMakeRoomFor to expand the querybuf, but later in some cases it uses that query buffer as is for an argv element (see "Optimization"), which means that the sds in argv may have a lot of wasted space, and then in case modules keep that argv RedisString inside their data structure, this space waste will remain for long (until restarted from rdb).
-
- 01 Feb, 2019 2 commits
-
-
antirez authored
It does not make much sense to limit what modules can do: the admin should instead limit what module commnads an user may call. So RedisModule_Call() and other module operations should be able to execute everything they want: the limitation should be posed by the API exported by the module itself.
-
antirez authored
-
- 09 Jan, 2019 1 commit
-
-
antirez authored
The function naming was totally nuts. Let's fix it as we break PRs anyway with RESP3 refactoring and changes.
-