1. 11 Mar, 2014 3 commits
    • Matt Stancliff's avatar
      Fix return value check for anetTcpAccept · 7c359449
      Matt Stancliff authored
      anetTcpAccept returns ANET_ERR, not AE_ERR.
      
      This isn't a physical error since both ANET_ERR
      and AE_ERR are -1, but better to be consistent.
      7c359449
    • Matt Stancliff's avatar
      Bind source address for cluster communication · 9a7cf319
      Matt Stancliff authored
      The first address specified as a bind parameter
      (server.bindaddr[0]) gets used as the source IP
      for cluster communication.
      
      If no bind address is specified by the user, the
      behavior is unchanged.
      
      This patch allows multiple Redis Cluster instances
      to communicate when running on the same interface
      of the same host.
      9a7cf319
    • Matt Stancliff's avatar
      Cluster: error out quicker if port is unusable · a0ea8f23
      Matt Stancliff authored
      The default cluster control port is 10,000 ports higher than
      the base Redis port.  If Redis is started on a too-high port,
      Cluster can't start and everything will exit later anyway.
      a0ea8f23
  2. 05 Mar, 2014 1 commit
    • antirez's avatar
      Fix configEpoch assignment when a cluster slot gets "closed". · e4833ed8
      antirez authored
      This is still code to rework in order to use agreement to obtain a new
      configEpoch when a slot is migrated, however this commit handles the
      special case that happens when the nodes are just started and everybody
      has a configEpoch of 0. In this special condition to have the maximum
      configEpoch is not enough as the special epoch 0 is not unique (all the
      others are).
      
      This does not fixes the intrinsic race condition of a failover happening
      while we are resharding, that will be addressed later.
      e4833ed8
  3. 11 Feb, 2014 5 commits
  4. 10 Feb, 2014 13 commits
  5. 07 Feb, 2014 1 commit
    • antirez's avatar
      Cluster: keys slot computation now supports hash tags. · 142281dc
      antirez authored
      Currently this is marginally useful, only to make sure two keys are in
      the same hash slot when the cluster is stable (no rehashing in
      progress).
      
      In the future it is possible that support will be added to run
      mutli-keys operations with keys in the same hash slot.
      142281dc
  6. 05 Feb, 2014 5 commits
  7. 31 Jan, 2014 1 commit
  8. 30 Jan, 2014 3 commits
  9. 29 Jan, 2014 8 commits