1. 20 Mar, 2020 1 commit
  2. 18 Mar, 2020 1 commit
    • WuYunlong's avatar
      Fix master replica inconsistency for upgrading scenario. · f6029fb9
      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.
      f6029fb9
  3. 16 Mar, 2020 4 commits
  4. 15 Mar, 2020 3 commits
  5. 13 Mar, 2020 1 commit
  6. 12 Mar, 2020 3 commits
  7. 11 Mar, 2020 1 commit
  8. 07 Mar, 2020 1 commit
  9. 05 Mar, 2020 1 commit
  10. 04 Mar, 2020 4 commits
  11. 03 Mar, 2020 1 commit
  12. 02 Mar, 2020 1 commit
  13. 29 Feb, 2020 1 commit
  14. 28 Feb, 2020 2 commits
  15. 27 Feb, 2020 4 commits
  16. 25 Feb, 2020 1 commit
  17. 24 Feb, 2020 1 commit
  18. 23 Feb, 2020 2 commits
  19. 22 Feb, 2020 3 commits
  20. 19 Feb, 2020 2 commits
  21. 18 Feb, 2020 2 commits
    • Oran Agra's avatar
      Defrag big lists in portions to avoid latency and freeze · 485425ce
      Oran Agra authored
      When active defrag kicks in and finds a big list, it will create a bookmark to
      a node so that it is able to resume iteration from that node later.
      
      The quicklist manages that bookmark, and updates it in case that node is deleted.
      
      This will increase memory usage only on lists of over 1000 (see
      active-defrag-max-scan-fields) quicklist nodes (1000 ziplists, not 1000 items)
      by 16 bytes.
      
      In 32 bit build, this change reduces the maximum effective config of
      list-compress-depth and list-max-ziplist-size (from 32767 to 8191)
      485425ce
    • hwware's avatar
      add missing subcommand description for debug oom · 7d4ebe11
      hwware authored
      7d4ebe11