- 06 5月, 2015 1 次提交
-
-
由 Salvatore Sanfilippo 提交于
fix compile error for struct msghdr in FreeBSD 10
-
- 05 5月, 2015 5 次提交
-
-
由 antirez 提交于
Probably this stuff should be called CLIENT_* in order to cross merge more easily.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 clark.kang 提交于
-
由 antirez 提交于
-
- 04 5月, 2015 6 次提交
-
-
由 Salvatore Sanfilippo 提交于
fix sds.c
-
由 Salvatore Sanfilippo 提交于
update copyright year
-
由 therealbill 提交于
Originally, only the +slave event which occurs when a slave is reconfigured during sentinelResetMasterAndChangeAddress triggers a flush of the config to disk. However, newly discovered slaves don't apparently trigger this flush but do trigger the +slave event issuance. So if you start up a sentinel, add a master, then add a slave to the master (as a way to reproduce it) you'll see the +slave event issued, but the sentinel config won't be updated with the known-slave entry. This change makes sentinel do the flush of the config if a new slave is deteted in sentinelRefreshInstanceInfo.
-
由 antirez 提交于
To rewrite the config in the loop that adds slaves back after a master reset, in order to handle switching to another master, is useless: it just adds latency since there is an fsync call in the inner loop, without providing any additional guarantee, but the contrary, since if after the first loop iteration the server crashes we end with just a single slave entry losing all the other informations. It is wiser to rewrite the config at the end when the full new state is configured.
-
由 Salvatore Sanfilippo 提交于
Fix Redis server crash when Lua command exceeds client output buffer limit.
-
由 Salvatore Sanfilippo 提交于
fix sentinel memory leak
-
- 29 4月, 2015 4 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
As suggested in #2543.
-
由 Salvatore Sanfilippo 提交于
Fix spelling and grammatical errors in readme
-
由 antirez 提交于
This fixes issue #2535, that was actually an hiredis library bug (I submitted an issue and fix to the redis/hiredis repo as well). When an asynchronous hiredis connection subscribes to a Pub/Sub channel and gets an error, and in other related conditions, the function redisProcessCallbacks() enters a code path where the link is disconnected, however the function returns before freeing the allocated reply object. This causes a memory leak. The memory leak was trivial to trigger in Redis Sentinel, which uses hiredis, every time we tried to subscribe to an instance that required a password, in case the Sentinel was configured either with the wrong password or without password at all. In this case, the -AUTH error caused the leaking code path to be executed. It was verified with Valgrind that after this change the leak no longer happens in Sentinel with a misconfigured authentication password.
-
- 28 4月, 2015 3 次提交
-
-
由 clark.kang 提交于
-
由 Jan-Erik Rediger 提交于
-
由 Jan-Erik Rediger 提交于
Closes #2549
-
- 27 4月, 2015 3 次提交
- 26 4月, 2015 1 次提交
-
-
由 Yossi Gottlieb 提交于
limit.
-
- 24 4月, 2015 2 次提交
-
-
由 Salvatore Sanfilippo 提交于
Added reference to IANA ticket for port 6379
-
由 Itamar Haber 提交于
Just so it's extra official
😄
-
- 21 4月, 2015 1 次提交
-
-
由 Itamar Haber 提交于
-
- 20 4月, 2015 2 次提交
-
-
由 FuGangqiang 提交于
-
由 FuGangqiang 提交于
-
- 19 4月, 2015 1 次提交
-
-
由 FuGangqiang 提交于
-
- 01 4月, 2015 4 次提交
-
-
由 antirez 提交于
When we fail to setup the write handler it does not make sense to take the client around, it is missing writes: whatever is a client or a slave anyway the connection should terminated ASAP. Moreover what the function does exactly with its return value, and in which case the write handler is installed on the socket, was not clear, so the functions comment are improved to make the goals of the function more obvious. Also related to #2485.
-
由 Salvatore Sanfilippo 提交于
fixes to diskless replication.
-
由 antirez 提交于
This should likely fix a false positive when running with the --valgrind option.
-
由 Oran Agra 提交于
master was closing the connection if the RDB transfer took long time. and also sent PINGs to the slave before it got the initial ACK, in which case the slave wouldn't be able to find the EOF marker.
-
- 31 3月, 2015 1 次提交
-
-
由 antirez 提交于
Segfault introduced during a refactoring / warning suppression a few commits away. This particular call assumed that it is safe to pass NULL to the object pointer argument when we are sure the set has a given encoding. This can't be assumed and is now guaranteed to segfault because of the new API of setTypeNext().
-
- 30 3月, 2015 4 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
This change fixes several warnings compiling at -O3 level with GCC 4.8.2, and at the same time, in case of misuse of the API, we have the pointer initialize to NULL or the integer initialized to the value -123456789 which is easy to spot by naked eye.
-
由 antirez 提交于
Another one just to avoid a warning. Slightly more defensive code anyway.
-
由 antirez 提交于
Change done in order to remove a warning and improve code robustness. No actual bug here.
-
- 27 3月, 2015 2 次提交