- 21 Feb, 2013 8 commits
- 20 Feb, 2013 5 commits
- 15 Feb, 2013 8 commits
- 14 Feb, 2013 7 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
This makes us able to avoid allocating the cluster state structure if cluster is not enabled, but still we can handle the configuration directive that sets the cluster config filename.
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
- 13 Feb, 2013 3 commits
- 12 Feb, 2013 9 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
When we are preparing an handshake with the slave we can't touch the connection buffer as it'll be used to accumulate differences between the sent RDB file and what arrives next from clients. So in short we can't use addReply() family functions. However we just use write(2) because we know that the socket buffer is empty, since a prerequisite for SYNC to work is that the static buffer and the output list are empty, and in general it is not expected that a client SYNCs after doing some heavy I/O with the master. However a short write connection is explicitly handled to avoid fragility (we simply close the connection and the slave will retry).
-