- 31 Jul, 2019 1 commit
-
-
antirez authored
-
- 30 Jul, 2019 4 commits
-
-
Salvatore Sanfilippo authored
Implement module api for aux data in rdb
-
Salvatore Sanfilippo authored
Reduce the calling stack
-
antirez authored
This was broken since a refactoring performed recently by myself.
-
Salvatore Sanfilippo authored
Fix HLL corruption bug
-
- 29 Jul, 2019 1 commit
-
-
John Sully authored
-
- 25 Jul, 2019 3 commits
-
-
antirez authored
-
antirez authored
-
Salvatore Sanfilippo authored
RM_Log - add support for logging without a context or context without module
-
- 24 Jul, 2019 6 commits
- 23 Jul, 2019 6 commits
-
-
Salvatore Sanfilippo authored
Removed unnecessary creation of Redis objects
-
antirez authored
-
antirez authored
-
Salvatore Sanfilippo authored
Client side caching: do not reclaim tracking table if it's empty
-
zhaozhao.zz authored
-
Madelyn Olson authored
-
- 22 Jul, 2019 8 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
-
- 19 Jul, 2019 1 commit
-
-
antirez authored
Thanks to @JohnSully for noticing this problem.
-
- 18 Jul, 2019 5 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.
-
Salvatore Sanfilippo authored
Tracking flushdb
-
antirez authored
-
zhaozhao.zz authored
-
- 17 Jul, 2019 5 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
Oran Agra authored
now that replica can read rdb directly from the socket, it should avoid exiting on short read and instead try to re-sync. this commit tries to have minimal effects on non-diskless rdb reading. and includes a test that tries to trigger this scenario on various read cases.
-