- 06 May, 2019 4 commits
-
-
antirez authored
-
antirez authored
-
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.
-
- 28 Mar, 2019 1 commit
-
-
David Carlier authored
-
- 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 1 commit
-
-
Oran Agra authored
-
- 27 Feb, 2019 1 commit
-
-
antirez authored
As documented but never implemented.
-
- 25 Feb, 2019 5 commits
- 21 Feb, 2019 2 commits
-
-
antirez authored
-
Madelyn Olson authored
-
- 12 Feb, 2019 2 commits
-
-
antirez authored
Related to #5832.
-
zhaozhao.zz authored
-
- 18 Jan, 2019 1 commit
-
-
antirez authored
-
- 15 Jan, 2019 1 commit
-
-
antirez authored
-
- 11 Jan, 2019 1 commit
-
-
antirez authored
-
- 10 Jan, 2019 1 commit
-
-
antirez authored
-
- 09 Jan, 2019 14 commits
-
-
antirez authored
-
antirez authored
The function naming was totally nuts. Let's fix it as we break PRs anyway with RESP3 refactoring and changes.
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
- 11 Dec, 2018 1 commit
-
-
antirez authored
See #5663.
-
- 07 Dec, 2018 1 commit
-
-
zhaozhao.zz authored
-
- 04 Dec, 2018 1 commit
-
-
Madelyn Olson authored
-
- 30 Oct, 2018 1 commit
-
-
antirez authored
Fake clients are used in special situations and are not linked to the normal clients list, freeing them will always result in Redis crashing in one way or the other. It's not common to send replies to fake clients, but we have one usage in the modules API. When a client is blocked, we associate to the blocked client object (that is safe to manipulate in a thread), a fake client that accumulates replies. So because of this bug there was the problem described in issue #5443. The fix was verified to work with the provided example module. To write a regression is very hard and unlikely to be triggered in the future.
-
- 09 Oct, 2018 1 commit
-
-
zhaozhao.zz authored
-