1. 02 Apr, 2020 1 commit
  2. 01 Apr, 2020 6 commits
  3. 31 Mar, 2020 11 commits
  4. 30 Mar, 2020 2 commits
  5. 29 Mar, 2020 1 commit
  6. 28 Mar, 2020 3 commits
  7. 27 Mar, 2020 9 commits
  8. 26 Mar, 2020 1 commit
  9. 25 Mar, 2020 5 commits
    • Oran Agra's avatar
      AOFRW on an empty stream created with MKSTREAM loads badkly · 3b29556a
      Oran Agra authored
      the AOF will be loaded successfully, but the stream will be missing,
      i.e inconsistencies with the original db.
      
      this was because XADD with id of 0-0 would error.
      
      add a test to reproduce.
      3b29556a
    • antirez's avatar
      PSYNC2: meaningful offset test. · c4d7f30e
      antirez authored
      c4d7f30e
    • antirez's avatar
      PSYNC2: meaningful offset implemented. · 57fa355e
      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.
      57fa355e
    • antirez's avatar
      Explain why we allow transactions in -BUSY state. · f15042db
      antirez authored
      Related to #7022.
      f15042db
    • Salvatore Sanfilippo's avatar
      Merge pull request #7022 from oranagra/multi-busy-script · 643bc48a
      Salvatore Sanfilippo authored
      MULTI/EXEC during LUA script timeout are messed up
      643bc48a
  10. 23 Mar, 2020 1 commit
    • Oran Agra's avatar
      MULTI/EXEC during LUA script timeout are messed up · ec007559
      Oran Agra authored
      Redis refusing to run MULTI or EXEC during script timeout may cause partial
      transactions to run.
      
      1) if the client sends MULTI+commands+EXEC in pipeline without waiting for
      response, but these arrive to the shards partially while there's a busy script,
      and partially after it eventually finishes: we'll end up running only part of
      the transaction (since multi was ignored, and exec would fail).
      
      2) similar to the above if EXEC arrives during busy script, it'll be ignored and
      the client state remains in a transaction.
      
      the 3rd test which i added for a case where MULTI and EXEC are ok, and
      only the body arrives during busy script was already handled correctly
      since processCommand calls flagTransaction
      ec007559