- 23 Oct, 2019 22 commits
-
-
antirez authored
Calling a module hook callback may result in callback operations in turn triggering other events the module is subscribed too. We don't want to trigger those, it's unsafe and quite confusing, and to do it correcly we would need to maintain an event list: quite a more complex implementation.
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
In 32 bit systems casting to "long" will cut the result to 32 bit.
-
- 17 Oct, 2019 3 commits
- 16 Oct, 2019 4 commits
-
-
Salvatore Sanfilippo authored
Abstract Connections I/O API & TLS Support
-
Yossi Gottlieb authored
-
Yossi Gottlieb authored
-
Salvatore Sanfilippo authored
Addition of RedisModule_OnUnload hook
-
- 15 Oct, 2019 3 commits
-
-
Yossi Gottlieb authored
-
Yossi Gottlieb authored
-
Yossi Gottlieb authored
-
- 10 Oct, 2019 8 commits
-
-
antirez authored
-
Salvatore Sanfilippo authored
[trivial] fix typos salves to slaves in replication.c
-
Salvatore Sanfilippo authored
there should is AUTH && HELLO non authenticated state.
-
Salvatore Sanfilippo authored
Fix usage of server.stream_node_max_*
-
Salvatore Sanfilippo authored
purge jemalloc after flush, and enable background purging thread
-
Salvatore Sanfilippo authored
resolve typo in test module
-
antirez authored
-
antirez authored
This is what happened: 1. Instance starts, is a slave in the cluster configuration, but actually server.masterhost is not set, so technically the instance is acting like a master. 2. loadDataFromDisk() calls replicationCacheMasterUsingMyself() even if the instance is a master, in the case it is logically a slave and the cluster is enabled. So now we have a cached master even if the instance is practically configured as a master (from the POV of server.masterhost value and so forth). 3. clusterCron() sees that the instance requires to replicate from its master, because logically it is a slave, so it calls replicationSetMaster() that will in turn call replicationCacheMasterUsingMyself(): before this commit, this call would overwrite the old cached master, creating a memory leak.
-