1. 12 Feb, 2013 9 commits
    • antirez's avatar
      89b48f08
    • antirez's avatar
      PSYNC: don't use the client buffer to send +CONTINUE and +FULLRESYNC. · 0ed6daa4
      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).
      0ed6daa4
    • antirez's avatar
    • antirez's avatar
    • antirez's avatar
      41d64a75
    • antirez's avatar
      07888202
    • antirez's avatar
      Use the new unified protocol to send SELECT to slaves. · e34a35a5
      antirez authored
      SELECT was still transmitted to slaves using the inline protocol, that
      is conceived mostly for humans to type into telnet sessions, and is
      notably not understood by redis-cli --slave.
      
      Now the new protocol is used instead.
      e34a35a5
    • antirez's avatar
      Use replicationFeedSlaves() to send PING to slaves. · 4b83ad4e
      antirez authored
      A Redis master sends PING commands to slaves from time to time: doing
      this ensures that even if absence of writes, the master->slave channel
      remains active and the slave can feel the master presence, instead of
      closing the connection for timeout.
      
      This commit changes the way PINGs are sent to slaves in order to use the
      standard interface used to replicate all the other commands, that is,
      the function replicationFeedSlaves().
      
      With this change the stream of commands sent to every slave is exactly
      the same regardless of their exact state (Transferring RDB for first
      synchronization or slave already online). With the previous
      implementation the PING was only sent to online slaves, with the result
      that the output stream from master to slaves was not identical for all
      the slaves: this is a problem if we want to implement partial resyncs in
      the future using a global replication stream offset.
      
      TL;DR: this commit should not change the behaviour in practical terms,
      but is just something in preparation for partial resynchronization
      support.
      4b83ad4e
    • antirez's avatar
      Emit SELECT to slaves in a centralized way. · 7465ac7a
      antirez authored
      Before this commit every Redis slave had its own selected database ID
      state. This was not actually useful as the emitted stream of commands
      is identical for all the slaves.
      
      Now the the currently selected database is a global state that is set to
      -1 when a new slave is attached, in order to force the SELECT command to
      be re-emitted for all the slaves.
      
      This change is useful in order to implement replication partial
      resynchronization in the future, as makes sure that the stream of
      commands received by slaves, including SELECT commands, are exactly the
      same for every slave connected, at any time.
      
      In this way we could have a global offset that can identify a specific
      piece of the master -> slaves stream of commands.
      7465ac7a
  2. 11 Feb, 2013 1 commit
  3. 08 Feb, 2013 4 commits
  4. 07 Feb, 2013 1 commit
  5. 05 Feb, 2013 3 commits
    • antirez's avatar
      b70b459b
    • charsyam's avatar
      Turn off TCP_NODELAY on the slave socket after SYNC. · c85647f3
      charsyam authored
      Further details from @antirez:
      
      It was reported by @StopForumSpam on Twitter that the Redis replication
      link was strangely using multiple TCP packets for multiple commands.
      This wastes a lot of bandwidth and is due to the TCP_NODELAY option we
      enable on the socket after accepting a new connection.
      
      However the master -> slave channel is a one-way channel since Redis
      replication is asynchronous, so there is no point in trying to reduce
      the latency, we should aim to reduce the bandwidth. For this reason this
      commit introduces the ability to disable the nagle algorithm on the
      socket after a successful SYNC.
      
      This feature is off by default because the delay can be up to 40
      milliseconds with normally configured Linux kernels.
      c85647f3
    • Rock Li's avatar
      retval doesn't initalized · 8063155c
      Rock Li authored
      If each if conditions are all fail, variable retval will under uninitlized
      8063155c
  6. 04 Feb, 2013 1 commit
    • Gengliang Wang's avatar
      Fix a bug in srandmemberWithCountCommand() · 00274733
      Gengliang Wang authored
      In CASE 2, the call sunionDiffGenericCommand will involve the string "srandmember" 
      > sadd foo one
      (integer 1)
      > sadd srandmember two
      (integer 2)
      > srandmember foo 3
      1)"one"
      2)"two"
      00274733
  7. 31 Jan, 2013 1 commit
  8. 29 Jan, 2013 2 commits
  9. 28 Jan, 2013 12 commits
  10. 21 Jan, 2013 4 commits
    • antirez's avatar
      88015b89
    • antirez's avatar
      UNSUBSCRIBE and PUNSUBSCRIBE: always provide a reply. · 2039f1a3
      antirez authored
      UNSUBSCRIBE and PUNSUBSCRIBE commands are designed to mass-unsubscribe
      the client respectively all the channels and patters if called without
      arguments.
      
      However when these functions are called without arguments, but there are
      no channels or patters we are subscribed to, the old behavior was to
      don't reply at all.
      
      This behavior is broken, as every command should always reply.
      Also it is possible that we are no longer subscribed to a channels but we
      are subscribed to patters or the other way around, and the client should
      be notified with the correct number of subscriptions.
      
      Also it is not pretty that sometimes we did not receive a reply at all
      in a redis-cli session from these commands, blocking redis-cli trying
      to read the reply.
      
      This fixes issue #714.
      2039f1a3
    • antirez's avatar
      Fixed a bug in memtest progress bar, that had no actual effects. · 93f61bb2
      antirez authored
      This closes issue #859, thanks to @erbenmo.
      93f61bb2
    • antirez's avatar
      Not every __sun has backtrace(). · cd892d01
      antirez authored
      I don't know how to test for Open Solaris that has support for
      backtrace() so for now removing the #ifdef that breaks compilation under
      other Solaris flavors.
      cd892d01
  11. 19 Jan, 2013 2 commits
    • antirez's avatar
      Additionally two typos fixed thanks to @jodal · e50cdbe4
      antirez authored
      e50cdbe4
    • antirez's avatar
      Whitelist SIGUSR1 to avoid auto-triggering errors. · 79a0ef62
      antirez authored
      This commit fixes issue #875 that was caused by the following events:
      
      1) There is an active child doing BGSAVE.
      2) flushall is called (or any other condition that makes Redis killing
      the saving child process).
      3) An error is sensed by Redis as the child exited with an error (killed
      by a singal), that stops accepting write commands until a BGSAVE happens
      to be executed with success.
      
      Whitelisting SIGUSR1 and making sure Redis always uses this signal in
      order to kill its own children fixes the issue.
      79a0ef62