1. 02 May, 2014 3 commits
  2. 30 Apr, 2014 3 commits
  3. 29 Apr, 2014 8 commits
    • antirez's avatar
      CLUSTER SET-CONFIG-EPOCH implemented. · 11d9ecb7
      antirez authored
      Initially Redis Cluster accepted that after cluster creation all the
      nodes were at configEpoch 0, evolving from zero as failovers happen.
      
      However later the semantic was made more strict in order to make sure a
      cluster has always all the master nodes with a different configEpoch,
      which is more robust in some corner case (especially resulting from
      errors by the system administrator).
      
      To assign different configEpochs to different nodes at startup was a
      task performed naturally by the config conflicts resolution algorithm
      (see the Cluster specification). However this works well only for small
      clusters or when there are actually just a few collisions, since it is
      designed for exceptional cases.
      
      When a large cluster is created hundred of nodes can be at epoch 0, so
      the conflict resolution code is slow to provide an unique config to each
      node. For this reason this new command was introduced. It can be called
      only when a node is totally fresh: no other nodes known, and configEpoch
      set to zero, so it is safe even against misuses.
      
      redis-trib will use the new command in order to start the cluster
      already setting an incremental unique config to every node.
      11d9ecb7
    • antirez's avatar
      Cluster test: slots allocation. · 7b5ce1ff
      antirez authored
      7b5ce1ff
    • antirez's avatar
      Cluster test: use 20 instances. · 4a3db255
      antirez authored
      This makes tests a bit slower, but it is better to test things at a
      decent scale instead of using just a few nodes, and for a few tests we
      actually need so many nodes.
      4a3db255
    • antirez's avatar
      e8631a69
    • antirez's avatar
      Cluster test: config epoch conflict resolution. · 9e422f74
      antirez authored
      9e422f74
    • antirez's avatar
      Cluster test: auto-discovery to form full mesh. · 2c556223
      antirez authored
      2c556223
    • antirez's avatar
      2555b2f4
    • antirez's avatar
      e1b12981
  4. 28 Apr, 2014 4 commits
  5. 24 Apr, 2014 10 commits
  6. 23 Apr, 2014 5 commits
  7. 22 Apr, 2014 3 commits
  8. 18 Apr, 2014 3 commits
  9. 17 Apr, 2014 1 commit
    • antirez's avatar
      Speedup hllRawSum() processing 8 bytes per iteration. · 5eb7ac0c
      antirez authored
      The internal HLL raw encoding used by PFCOUNT when merging multiple keys
      is aligned to 8 bits (1 byte per register) so we can exploit this to
      improve performances by processing multiple bytes per iteration.
      
      In benchmarks the new code was several times faster with HLLs with many
      registers set to zero, while no slowdown was observed with populated
      HLLs.
      5eb7ac0c