1. 16 Dec, 2014 1 commit
  2. 15 Dec, 2014 1 commit
  3. 11 Dec, 2014 2 commits
  4. 10 Dec, 2014 1 commit
    • antirez's avatar
      Better read-only behavior for expired keys in slaves. · 06e76bc3
      antirez authored
      Slaves key expire is orchestrated by the master. Sometimes the master
      will send the synthesized DEL to expire keys on the slave with a non
      trivial delay (when the key is not accessed, only the incremental expiry
      algorithm will expire it in background).
      
      During that time, a key is logically expired, but slaves still return
      the key if you GET (or whatever) it. This is a bad behavior.
      
      However we can't simply trust the slave view of the key, since we need
      the master to be able to send write commands to update the slave data
      set, and DELs should only happen when the key is expired in the master
      in order to ensure consistency.
      
      However 99.99% of the issues with this behavior is when a client which
      is not a master sends a read only command. In this case we are safe and
      can consider the key as non existing.
      
      This commit does a few changes in order to make this sane:
      
      1. lookupKeyRead() is modified in order to return NULL if the above
      conditions are met.
      2. Calls to lookupKeyRead() in commands actually writing to the data set
      are repliaced with calls to lookupKeyWrite().
      
      There are redundand checks, so for example, if in "2" something was
      overlooked, we should be still safe, since anyway, when the master
      writes the behavior is to don't care about what expireIfneeded()
      returns.
      
      This commit is related to  #1768, #1770, #2131.
      06e76bc3
  5. 28 Nov, 2014 1 commit
    • antirez's avatar
      Cluster PUBLISH message: fix totlen count. · 669aa2a2
      antirez authored
      bulk_data field size was not removed from the count. It is not possible
      to declare it simply as 'char bulk_data[]' since the structure is nested
      into another structure.
      669aa2a2
  6. 29 Oct, 2014 2 commits
    • Matt Stancliff's avatar
      Networking: add more outbound IP binding fixes · 0014966c
      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).
      0014966c
    • Matt Stancliff's avatar
      Parse cluster state file in IPv6 compatible way · daca1edb
      Matt Stancliff authored
      We need to pick the port based on the _last_ colon, not the first one.
      daca1edb
  7. 08 Oct, 2014 2 commits
    • antirez's avatar
      Cluster: process gossip section only for known nodes. · 5f6950ca
      antirez authored
      With the exception of nodes sending MEET packets: we have to trust them
      since they can send us MEET packets only when the cluster is initially
      created or because sysadmin manual action.
      5f6950ca
    • antirez's avatar
      Cluster: fix logic to detect we are among a minority. · 36e34a65
      antirez authored
      In the cluster evaluation function we are supposed to set the cluster
      state as "fail" if we are among a minority, however the code was not
      detecting to be into a minority partition if exactly half the masters
      were reachable, which is a minority.
      36e34a65
  8. 07 Oct, 2014 1 commit
  9. 29 Sep, 2014 1 commit
    • Matt Stancliff's avatar
      Clean up text throughout project · 12d0195b
      Matt Stancliff authored
        - Remove trailing newlines from redis.conf
        - Fix comment misspelling
        - Clarifies zipEncodeLength usage and a C API mention (#1243, #1242)
        - Fix cluster typos (inspired by @papanikge #1507)
        - Fix rewite -> rewrite in a few places (inspired by #682)
      
      Closes #1243, #1242, #1507
      12d0195b
  10. 17 Sep, 2014 2 commits
  11. 25 Aug, 2014 1 commit
    • Matt Stancliff's avatar
      Cluster: Fix segfault if cluster config corrupt · 60c448b5
      Matt Stancliff authored
      This commit adds a size check after initial config
      line parsing to make sure we have *at least* 8 arguments
      per line.
      
      Also, instead of asserting for cluster->myself, we just test
      and error out normally (since the error does a hard exit anyway).
      
      Closes #1597
      60c448b5
  12. 18 Aug, 2014 2 commits
  13. 13 Aug, 2014 1 commit
  14. 08 Aug, 2014 3 commits
  15. 25 Jul, 2014 1 commit
    • antirez's avatar
      Cluster: don't migrate to a master that never had slaves. · 0d9bcb1c
      antirez authored
      Replica migration algorithm modified so that slaves never try to migrate
      to masters that were never configured to have slaves in the past.
      We want the algorithm to take care of masters that remained without
      *working* slaves, but that used to have slaves according to the cluster
      configuration.
      0d9bcb1c
  16. 22 Jul, 2014 1 commit
    • antirez's avatar
      CLUSTER RESET: Flush dataset if node is a slave. · 89af4631
      antirez authored
      For non-empty masters, CLUSTER RESET is denied, and the user requires to
      start to reset a node by explicitly clearing it with FLUSHALL.
      However CLUSTER RESET when executed with slaves don't have this
      restrictions since data is just a replica of the master, and with
      read-only slaves it is also not possible to remove the data set. However
      the node was turned from slave to master after a reset, without touching
      the old slave data. This is 99.99% of times not appropriate and forces
      full resets to follow this path to work with both slave and master
      nodes:
      
          FLUSHALL
          CLUSTER RESET HARD
          FLUSHALL
      
      Since we need the first flushall for masters, and the second for slaves.
      
      This commit changes the behavior so that CLUSTER RESET removes the data set
      of a slave node during a reset, in the moment it gets turned into a master,
      so the new pattern is simply:
      
          FLUSHALL (that may fail for slaves)
          CLUSTER RESET
      89af4631
  17. 26 Jun, 2014 1 commit
  18. 25 Jun, 2014 4 commits
    • antirez's avatar
      CLUSTER SLOTS: don't output failing slaves. · 75c57d53
      antirez authored
      While we have to output failing masters in order to provide an accurate
      map (that may be the one of a Redis Cluster in down state because not
      all slots are served by a working master), to provide slaves in FAIL
      state is not a good idea since those are not necesarely needed, and the
      client will likely incur into a latency penalty trying to connect with a
      slave which is down.
      
      Note that this means that CLUSTER SLOTS does not provide a *complete*
      map of slaves, however this would not be of any help since slaves may be
      added later, and a client that needs to scale reads and requires to
      stay updated with the list of slaves, need to do a refresh of the map
      from time to time, anyway.
      75c57d53
    • antirez's avatar
    • Matt Stancliff's avatar
      Cluster: Add CLUSTER SLOTS command · e14829de
      Matt Stancliff authored
      CLUSTER SLOTS returns a Redis-formatted mapping from
      slot ranges to IP/Port pairs serving that slot range.
      
      The outer return elements group return values by slot ranges.
      
      The first two entires in each result are the min and max slots for the range.
      
      The third entry in each result is guaranteed to be either
      an IP/Port of the master for that slot range - OR - null
      if that slot range, for some reason, has no master
      
      The 4th and higher entries in each result are replica instances
      for the slot range.
      
      Output comparison:
      127.0.0.1:7001> cluster nodes
      f853501ec8ae1618df0e0f0e86fd7abcfca36207 127.0.0.1:7001 myself,master - 0 0 2 connected 4096-8191
      5a2caa782042187277647661ffc5da739b3e0805 127.0.0.1:7005 slave f853501ec8ae1618df0e0f0e86fd7abcfca36207 0 1402622415859 6 connected
      6c70b49813e2ffc9dd4b8ec1e108276566fcf59f 127.0.0.1:7007 slave 26f4729ca0a5a992822667fc16b5220b13368f32 0 1402622415357 8 connected
      2bd5a0e3bb7afb2b56a2120d3fef2f2e4333de1d 127.0.0.1:7006 slave 32adf4b8474fdc938189dba00dc8ed60ce635b0f 0 1402622419373 7 connected
      5a9450e8279df36ff8e6bb1c139ce4d5268d1390 127.0.0.1:7000 master - 0 1402622418872 1 connected 0-4095
      32adf4b8474fdc938189dba00dc8ed60ce635b0f 127.0.0.1:7002 master - 0 1402622419874 3 connected 8192-12287
      5db7d05c245267afdfe48c83e7de899348d2bdb6 127.0.0.1:7004 slave 5a9450e8279df36ff8e6bb1c139ce4d5268d1390 0 1402622417867 5 connected
      26f4729ca0a5a992822667fc16b5220b13368f32 127.0.0.1:7003 master - 0 1402622420877 4 connected 12288-16383
      
      127.0.0.1:7001> cluster slots
      1) 1) (integer) 0
         2) (integer) 4095
         3) 1) "127.0.0.1"
            2) (integer) 7000
         4) 1) "127.0.0.1"
            2) (integer) 7004
      2) 1) (integer) 12288
         2) (integer) 16383
         3) 1) "127.0.0.1"
            2) (integer) 7003
         4) 1) "127.0.0.1"
            2) (integer) 7007
      3) 1) (integer) 4096
         2) (integer) 8191
         3) 1) "127.0.0.1"
            2) (integer) 7001
         4) 1) "127.0.0.1"
            2) (integer) 7005
      4) 1) (integer) 8192
         2) (integer) 12287
         3) 1) "127.0.0.1"
            2) (integer) 7002
         4) 1) "127.0.0.1"
            2) (integer) 7006
      e14829de
    • antirez's avatar
      Cluster: myself->ip autodiscovery. · f29b12d0
      antirez authored
      Instead of having an hardcoded IP address in the node configuration, we
      autodiscover it via MEET messages for automatic update when the node is
      restarted with a different IP address.
      
      This mechanism was discussed in the context of PR #1782.
      f29b12d0
  19. 23 Jun, 2014 1 commit
  20. 20 Jun, 2014 1 commit
  21. 10 Jun, 2014 6 commits
  22. 07 Jun, 2014 2 commits
    • antirez's avatar
      Cluster: check that configEpoch never goes back. · 32d0a79f
      antirez authored
      Since there are ways to alter the configEpoch outside of the failover
      procedure (for exampel CLUSTER SET-CONFIG-EPOCH and via the configEpoch
      collision resolution algorithm), make always sure, before replacing our
      configEpoch with a new one, that it is greater than the current one.
      32d0a79f
    • antirez's avatar
      Cluster: SET-CONFIG-EPOCH should update currentEpoch. · a2c2ef7d
      antirez authored
      SET-CONFIG-EPOCH, used by redis-trib at cluster creation time, failed to
      update the currentEpoch, making it possible after a failover for a
      server to set its configEpoch to a value smaller than the current one
      (since configEpochs are obtained using currentEpoch).
      
      The bug totally break the Redis Cluster algorithms and protocols
      allowing for permanent split brain conditions about the slots
      configuration as shown in issue #1799.
      a2c2ef7d
  23. 26 May, 2014 1 commit
  24. 22 May, 2014 1 commit