1. 27 May, 2013 5 commits
    • antirez's avatar
      Send ACK to master once every second. · 45e6a402
      antirez authored
      ACKs can be also used as a base for synchronous replication. However in
      that case they'll be explicitly requested by the master when the client
      sends a request that needs to be replicated synchronously.
      45e6a402
    • antirez's avatar
      Don't ACK the master after every command. · a74f8fe1
      antirez authored
      Sending an ACK is now moved into the replicationSendAck() function.
      a74f8fe1
    • antirez's avatar
      0000d533
    • antirez's avatar
      Replication: send REPLCONF ACK to master. · 146f1d7d
      antirez authored
      146f1d7d
    • antirez's avatar
      REPLCONF ACK command. · 1e77b77d
      antirez authored
      This special command is used by the slave to inform the master the
      amount of replication stream it currently consumed.
      
      it does not return anything so that we not need to consume additional
      bandwidth needed by the master to reply something.
      
      The master can do a number of things knowing the amount of stream
      processed, such as understanding the "lag" in bytes of the slave, verify
      if a given command was already processed by the slave, and so forth.
      1e77b77d
  2. 24 May, 2013 3 commits
  3. 18 May, 2013 1 commit
  4. 15 May, 2013 20 commits
  5. 14 May, 2013 1 commit
  6. 09 May, 2013 1 commit
  7. 08 May, 2013 5 commits
  8. 02 May, 2013 3 commits
  9. 30 Apr, 2013 1 commit
    • antirez's avatar
      Sentinel: changes to tilt mode. · e7bcec82
      antirez authored
      Tilt mode was too aggressive (not processing INFO output), this
      resulted in a few problems:
      
      1) Redirections were not followed when in tilt mode. This opened a
         window to misinform clients about the current master when a Sentinel
         was in tilt mode and a fail over happened during the time it was not
         able to update the state.
      
      2) It was possible for a Sentinel exiting tilt mode to detect a false
         fail over start, if a slave rebooted with a wrong configuration
         about at the same time. This used to happen since in tilt mode we
         lose the information that the runid changed (reboot).
      
         Now instead the Sentinel in tilt mode will still remove the instance
         from the list of slaves if it changes state AND runid at the same
         time.
      
      Both are edge conditions but the changes should overall improve the
      reliability of Sentinel.
      e7bcec82