- 31 Oct, 2014 3 commits
-
-
Mariano Pérez Rodríguez authored
Fix two typos in redis.conf: - "trnasfers" --> "transfers" - "enalbed" --> "enabled"
-
Salvatore Sanfilippo authored
Enable Cluster IPv6 Support
-
Salvatore Sanfilippo authored
Networking: add more outbound IP binding fixes
-
- 30 Oct, 2014 1 commit
-
-
Salvatore Sanfilippo authored
Fix redis-cli from exiting after idle connection breaks
-
- 29 Oct, 2014 6 commits
-
-
Matt Stancliff authored
Same as the original bind fixes (we just missed these the first time around). This helps Redis not automatically send connections from the first IP on an interface if we are bound to a specific IP address (e.g. with multiple IP aliases on one interface, you want to send from _your_ IP, not from the first IP on the interface).
-
Matt Stancliff authored
We need to pick the port based on the _last_ colon, not the first one.
-
Matt Stancliff authored
IP format is now any of: - 127.0.0.1:6379 - ::1:6379
-
Matt Stancliff authored
Closes #2066
-
antirez authored
-
antirez authored
This caused BGSAVE to be triggered a second time without any need when we switch from socket to disk target via the command CONFIG SET repl-diskless-sync no and there is already a slave waiting for the BGSAVE to start. Also comments clarified about what is happening.
-
- 27 Oct, 2014 6 commits
- 24 Oct, 2014 3 commits
- 23 Oct, 2014 1 commit
-
-
antirez authored
Child now reports full info to the parent including IDs of slaves in failure state and exit code.
-
- 22 Oct, 2014 3 commits
-
-
antirez authored
EWOULDBLOCK with the fdset rio target is returned when we try to write but the send timeout socket option triggered an error. Better to translate the error in something the user can actually recognize as a timeout.
-
antirez authored
We need to avoid that a child -> slaves transfer can continue forever. We use the same timeout used as global replication timeout, which is documented to also affect I/O operations during bulk transfers.
-
antirez authored
-
- 17 Oct, 2014 10 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
While the socket is set in blocking mode, we still can get short writes writing to a socket.
-
antirez authored
-
antirez authored
To perform a socket write() for each RDB rio API write call was extremely unefficient, so now rio has minimal buffering capabilities. Writes are accumulated into a buffer and only when a given limit is reacehd are actually wrote to the N slaves FDs. Trivia: rio lacked support for buffering since our targets were: 1) Memory buffers. 2) C standard I/O. Both were buffered already.
-
antirez authored
-
antirez authored
This is useful for normal replication in order to refresh the slave when we are persisting on disk, but for diskless replication the child is already receiving data while in WAIT_BGSAVE_END state.
-
antirez authored
-
antirez authored
-
antirez authored
-
- 16 Oct, 2014 6 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
If we turn from diskless to disk-based replication via CONFIG SET, we need a way to start a BGSAVE if there are slaves alerady waiting for a BGSAVE to start. Normally with disk-based replication we do it as soon as the previous child exits, but when there is a configuration change via CONFIG SET, we may have slaves in WAIT_BGSAVE_START state without an RDB background process currently active.
-
antirez authored
-
antirez authored
-
- 15 Oct, 2014 1 commit
-
-
antirez authored
-