1. 24 Apr, 2020 2 commits
    • antirez's avatar
      LCS -> STRALGO LCS. · 3722f89f
      antirez authored
      STRALGO should be a container for mostly read-only string
      algorithms in Redis. The algorithms should have two main
      characteristics:
      
      1. They should be non trivial to compute, and often not part of
      programming language standard libraries.
      2. They should be fast enough that it is a good idea to have optimized C
      implementations.
      
      Next thing I would love to see? A small strings compression algorithm.
      3722f89f
    • antirez's avatar
      Tracking: NOLOOP internals implementation. · 6791ff05
      antirez authored
      6791ff05
  2. 15 Apr, 2020 4 commits
  3. 07 Apr, 2020 5 commits
  4. 31 Mar, 2020 9 commits
  5. 25 Mar, 2020 4 commits
    • antirez's avatar
      PSYNC2: meaningful offset implemented. · 5f72f696
      antirez authored
      A very commonly signaled operational problem with Redis master-replicas
      sets is that, once the master becomes unavailable for some reason,
      especially because of network problems, many times it wont be able to
      perform a partial resynchronization with the new master, once it rejoins
      the partition, for the following reason:
      
      1. The master becomes isolated, however it keeps sending PINGs to the
      replicas. Such PINGs will never be received since the link connection is
      actually already severed.
      2. On the other side, one of the replicas will turn into the new master,
      setting its secondary replication ID offset to the one of the last
      command received from the old master: this offset will not include the
      PINGs sent by the master once the link was already disconnected.
      3. When the master rejoins the partion and is turned into a replica, its
      offset will be too advanced because of the PINGs, so a PSYNC will fail,
      and a full synchronization will be required.
      
      Related to issue #7002 and other discussion we had in the past around
      this problem.
      5f72f696
    • bodong.ybd's avatar
      b3e4abf0
    • WuYunlong's avatar
      Fix master replica inconsistency for upgrading scenario. · 0578157d
      WuYunlong authored
      Before this commit, when upgrading a replica, expired keys will not
      be loaded, thus causing replica having less keys in db. To this point,
      master and replica's keys is logically consistent. However, before
      the keys in master and replica are physically consistent, that is,
      they have the same dbsize, if master got a problem and the replica
      got promoted and becomes new master of that partition, and master
      updates a key which does not exist on master, but physically exists
      on the old master(new replica), the old master would refuse to update
      the key, thus causing master and replica data inconsistent.
      
      How could this happen?
      That's all because of the wrong judgement of roles while starting up
      the server. We can not use server.masterhost to judge if the server
      is master or replica, since it fails in cluster mode.
      
      When we start the server, we load rdb and do want to load expired keys,
      and do not want to have the ability to active expire keys, if it is
      a replica.
      0578157d
    • antirez's avatar
      ACL: Make Redis 6 more backward compatible with requirepass. · 9c2e42dd
      antirez authored
      Note that this as a side effect fixes Sentinel "requirepass" mode.
      9c2e42dd
  6. 05 Mar, 2020 2 commits
  7. 27 Feb, 2020 7 commits
  8. 12 Feb, 2020 7 commits