- 11 Jun, 2015 4 commits
-
-
antirez authored
We usually want to reach the master using the address of the interface Redis is bound to (via the "bind" config option). That's useful since the master will get (and publish) the slave address getting the peer name of the incoming socket connection from the slave. However, when this is not possible, for example because the slave is bound to the loopback interface but repliaces from a master accessed via an external interface, we want to still connect with the master even from a different interface: in this case it is not really important that the master will provide any other address, while it is vital to be able to replicate correctly. Related to issues #2609 and #2612.
-
antirez authored
This performs a best effort source address binding attempt. If it is possible to bind the local address and still have a successful connect(), then this socket is returned. Otherwise the call is retried without source address binding attempt. Related to issues #2609 and #2612.
-
antirez authored
Two code paths jumped to the "ok, return the socket to the user" code path to handle error conditions. Related to issues #2609 and #2612.
-
antirez authored
Related to issues #2609 and #2612.
-
- 03 Jun, 2015 3 commits
-
-
Ben Murphy authored
-
Ben Murphy authored
-
antirez authored
-
- 29 May, 2015 7 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
From Twitter: "@antirez that’s an awfully-named command :( http://en.wikipedia.org/wiki/Retching"
-
antirez authored
-
antirez authored
-
antirez authored
Normally ZADD only returns the number of elements added to a sorted set, using the RETCH option it returns the sum of elements added or for which the score was updated.
-
antirez authored
-
- 28 May, 2015 3 commits
-
-
antirez authored
-
Salvatore Sanfilippo authored
Update anet.c
-
Salvatore Sanfilippo authored
Removed incorrect suggestion
-
- 25 May, 2015 3 commits
-
-
Salvatore Sanfilippo authored
adding a sentinel command: "flushconfig" per RCP4
-
antirez authored
-
antirez authored
-
- 22 May, 2015 1 commit
-
-
antirez authored
This commit adds the SENTINEL simulate-failure, that sets specific hooks inside the state machine that will crash Sentinel, for testing purposes.
-
- 21 May, 2015 2 commits
-
-
Itamar Haber authored
DEL/INCR/DECR and others could be NTH but apparently never made it to the implementation of SORT
-
Huachao Huang authored
-
- 20 May, 2015 1 commit
-
-
antirez authored
Trivial omission of the obvious no-match case.
-
- 19 May, 2015 2 commits
- 18 May, 2015 1 commit
-
-
antirez authored
A way for monitoring systems to check that Sentinel is technically able to reach the quorum and failover, using the currently visible Sentinels.
-
- 15 May, 2015 4 commits
-
-
antirez authored
-
Salvatore Sanfilippo authored
Issue #2517, smove contract violation
-
Salvatore Sanfilippo authored
protocol error log should be seen by debug/verbose level
-
antirez authored
-
- 14 May, 2015 7 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
Otherwise pending commands callbacks will fire with a reference that no longer exists.
-
antirez authored
-
antirez authored
The PING trigger was improved again by using two fields instead of a single one to remember when the last ping was sent: 1. The "active" ping is the time at which we sent the last ping that still received no reply. However we continue to ping non replying instances even if they have an old active ping: the link may be disconnected and reconencted in the meantime so the older pings may get lost even if it's a TCP socket. 2. The "last" ping is the time at which we really sent the last ping on the wire, and this is used in order to throttle the amount of pings we send during failures (when no pong is received). All in all the failure detector effectiveness should be identical but we avoid to flood instances with pings during failures or when they are slow.
-
- 13 May, 2015 1 commit
-
-
antirez authored
-
- 12 May, 2015 1 commit
-
-
antirez authored
It's ok to ping as soon as the ping period has elapsed since we received the last PONG, but it's not good that we ping again if there is a pending ping... With this change we'll send a new ping if there is one pending only if two times the ping period elapsed since the ping which is still pending was sent.
-