- 05 Sep, 2019 2 commits
-
-
Oran Agra authored
When implementing the code that saves and loads these aux fields we used rdb format that was added for that in redis 5.0, but then we added the 'when' field which meant that the old redis-check-rdb won't be able to skip these. this fix adds an opcode as if that 'when' is part of the module data.
-
antirez authored
-
- 04 Sep, 2019 3 commits
-
-
antirez authored
Before this commit we may have not consumer buffers when a read error is encountered. Such buffers may contain errors that are important clues for the user: for instance a protocol error in the payload we send in pipe mode will cause the server to abort the connection. If the user does not get the protocol error, debugging what is happening can be a nightmare. This commit fixes issue #3756.
-
antirez authored
Currently useless but we release the fake client, so better to do a full cleanup. Thanks to @TomMD reporting this in #6353.
-
antirez authored
Thanks to @tnclong for reporting the problem.
-
- 02 Sep, 2019 2 commits
- 31 Aug, 2019 2 commits
- 07 Aug, 2019 1 commit
-
-
Oran Agra authored
-
- 05 Aug, 2019 1 commit
-
-
antirez authored
-
- 02 Aug, 2019 1 commit
-
-
zhaozhao.zz authored
-
- 31 Jul, 2019 3 commits
- 30 Jul, 2019 1 commit
-
-
antirez authored
This was broken since a refactoring performed recently by myself.
-
- 29 Jul, 2019 1 commit
-
-
John Sully authored
-
- 28 Jul, 2019 1 commit
-
-
David Carlier authored
-
- 24 Jul, 2019 2 commits
- 23 Jul, 2019 5 commits
-
-
antirez authored
-
antirez authored
-
zhaozhao.zz authored
-
Madelyn Olson authored
-
Madelyn Olson authored
-
- 22 Jul, 2019 9 commits
-
-
Oran Agra authored
Other changes: * fix memory leak in error handling of rdb loading of type OBJ_MODULE
-
antirez authored
-
antirez authored
This is extremely useful in order to simulate an high load of requests about different keys, and force Redis to track a lot of informations about several clients, to simulate real world workloads.
-
antirez authored
Now that the call also invalidates client side caching slots, it is important that after an internal flush operation we both send the notifications to the clients and, at the same time, are able to reclaim the memory of the tracking table. This may even fix a few edge cases related to MULTI/EXEC + WATCH during resync, not sure, but in general looks more correct.
-
antirez authored
-
antirez authored
Otherwise what happens is that the tracking table will never get garbage collected if there are no longer clients with tracking enabled. Now the invalidation function immediately checks if there is any table allocated, otherwise it returns ASAP, so the overhead when the feature is not used should be near zero.
-
antirez authored
-
antirez authored
-
chendianqiang authored
-
- 19 Jul, 2019 1 commit
-
-
antirez authored
Thanks to @JohnSully for noticing this problem.
-
- 18 Jul, 2019 4 commits
-
-
antirez authored
-
antirez authored
Without such change, the diskless replicas, when loading RDB files from the socket will not abort when a broken RDB file gets loaded. This is potentially unsafe, because right now Redis is not able to guarantee that encoding errors are safe from the POV of memory corruptions (for instance the LZF library may not be safe against untrusted data?) so better to abort when the RDB file we are going to load is corrupted. Instead I/O errors are still returned to the caller without aborting, so that in case of short read the diskless replica can try again.
-
antirez authored
-
zhaozhao.zz authored
-
- 17 Jul, 2019 1 commit
-
-
antirez authored
-