- 25 Sep, 2019 1 commit
-
-
antirez authored
-
- 18 Sep, 2019 1 commit
-
-
antirez authored
-
- 02 Sep, 2019 1 commit
-
-
antirez authored
-
- 31 Jul, 2019 1 commit
-
-
antirez authored
This was recently introduced with PR #6266.
-
- 24 Jul, 2019 1 commit
-
-
antirez authored
-
- 23 Jul, 2019 3 commits
-
-
antirez authored
-
antirez authored
-
Madelyn Olson authored
-
- 22 Jul, 2019 1 commit
-
-
antirez authored
-
- 10 Jul, 2019 1 commit
-
-
antirez authored
-
- 08 Jul, 2019 1 commit
-
-
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
-
- 03 Jul, 2019 1 commit
-
-
antirez authored
-
- 07 Jun, 2019 1 commit
-
-
Madelyn Olson authored
-
- 06 May, 2019 9 commits
-
-
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
-
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.
-
liaotonglang authored
sdsTest() defined in sds.c dit not match the call in server.c. remove it from REDIS_TEST, since test-sds defined in Makefile.
-
WuYunlong authored
-
- 20 Mar, 2019 1 commit
-
-
Oran Agra authored
also, airty for COMMAND command was wrong.
-
- 18 Mar, 2019 1 commit
-
-
Yossi Gottlieb authored
-
- 03 Mar, 2019 1 commit
-
-
Itamar Haber authored
-
- 27 Feb, 2019 1 commit
-
-
chendianqiang authored
-
- 25 Feb, 2019 1 commit
-
-
antirez authored
-
- 21 Feb, 2019 1 commit
-
-
antirez authored
-
- 13 Feb, 2019 2 commits
-
-
zhaozhao.zz authored
Adding another new filed categories at the end of command reply, it's easy to read and distinguish flags and categories, also compatible with old format.
-
antirez authored
That's not REALLY needed, but... right now with LASTSAVE being the only command tagged as "admin" but not "dangerous" what happens is that after rewrites the rewrite engine will produce from the rules: user default on +@all ~* -@dangerous nopass The rewrite: user default on nopass ~* +@all -@admin -@dangerous +lastsave Which is correct but will have users wondering about why LASTSAVE has something special. Since LASTSAVE after all also leaks information about the underlying server configuration, that may not be great for SAAS vendors, let's tag it as dangerous as well and forget about this issue :-)
-
- 12 Feb, 2019 1 commit
-
-
antirez authored
-
- 11 Feb, 2019 1 commit
-
-
antirez authored
The part that is fixed is that now if the default user is off whatever is its configuration the user is not considered authenticated.
-
- 07 Feb, 2019 1 commit
-
-
antirez authored
-
- 05 Feb, 2019 1 commit
-
-
antirez authored
-
- 04 Feb, 2019 1 commit
-
-
antirez authored
-
- 23 Jan, 2019 4 commits
- 22 Jan, 2019 1 commit
-
-
antirez authored
-