1. 18 Feb, 2016 4 commits
  2. 15 Feb, 2016 1 commit
  3. 10 Feb, 2016 2 commits
  4. 05 Feb, 2016 2 commits
  5. 29 Jan, 2016 2 commits
    • antirez's avatar
      Typo ASII -> ASCII fixed in comment. · 0c7c7631
      antirez authored
      0c7c7631
    • antirez's avatar
      Cluster: include node IDs in SLOTS output. · 0f3fb009
      antirez authored
      CLUSTER SLOTS now includes IDs in the nodes description associated with
      a given slot range. Certain client libraries implementations need a way
      to reference a node in an unique way, so they were relying on CLUSTER
      NODES, that is not a stable API and may change frequently depending on
      Redis Cluster future requirements.
      0f3fb009
  6. 28 Jan, 2016 2 commits
  7. 27 Jan, 2016 1 commit
    • antirez's avatar
      Sentinel: improve handling of known Sentinel instances. · 6bd409d0
      antirez authored
      1. Bug #3035 is fixed (NULL pointer access). This was happening with the
         folling set of conditions:
      
      * For some reason one of the Sentinels, let's call it Sentinel_A, changed ID (reconfigured from scratch), but is as the same address at which it used to be.
      
      * Sentinel_A performs a failover and/or has a newer configuration compared to another Sentinel, that we call, Sentinel_B.
      
      * Sentinel_B receives an HELLO message from Sentinel_A, where the address and/or ID is mismatched, but it is reporting a newer configuration for the master they are both monitoring.
      
      2. Sentinels now must have an ID otherwise they are not loaded nor persisted in the configuration. This allows to have conflicting Sentinels with the same address since now the master->sentinels dictionary is indexed by Sentinel ID.
      
      3. The code now detects if a Sentinel is annoucing itself with an IP/port pair already busy (of another Sentinel). The old Sentinel that had the same port/pair is set as having port 0, that means, the address is invalid. We may discover the right address later via HELLO messages.
      6bd409d0
  8. 26 Jan, 2016 6 commits
  9. 25 Jan, 2016 16 commits
  10. 19 Jan, 2016 1 commit
  11. 08 Jan, 2016 3 commits
    • antirez's avatar
      Scripting: handle trailing comments. · 5fd61c95
      antirez authored
      This fix, provided by Paul Kulchenko (@pkulchenko), allows the Lua
      scripting engine to evaluate statements with a trailing comment like the
      following one:
      
          EVAL "print() --comment" 0
      
      Lua can't parse the above if the string does not end with a newline, so
      now a final newline is always added automatically. This does not change
      the SHA1 of scripts since the SHA1 is computed on the body we pass to
      EVAL, without the other code we add to register the function.
      
      Close #2951.
      5fd61c95
    • antirez's avatar
      Allow MIGRATE to always be called on local keys for open slots. · d975baa3
      antirez authored
      Extend the MIGRATE extra freedom to be able to be called in the context
      of the local slot, anytime there is a slot open in one or the other
      direction (importing or migrating). This is useful for redis-trib to fix
      the cluster when it has in an odd state.
      
      Thix fix allows "redis-trib fix" to make its work in certain cases where
      previously an error was reported.
      d975baa3
    • antirez's avatar