1. 18 Mar, 2020 3 commits
    • Salvatore Sanfilippo's avatar
      Merge pull request #7001 from trevor211/fixDataInconsistency · 82e18077
      Salvatore Sanfilippo authored
      Fix data inconsistency
      82e18077
    • 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
    • WuYunlong's avatar
  2. 16 Mar, 2020 8 commits
  3. 15 Mar, 2020 4 commits
  4. 13 Mar, 2020 7 commits
  5. 12 Mar, 2020 5 commits
  6. 11 Mar, 2020 2 commits
  7. 10 Mar, 2020 2 commits
  8. 09 Mar, 2020 1 commit
  9. 07 Mar, 2020 1 commit
  10. 06 Mar, 2020 1 commit
  11. 05 Mar, 2020 5 commits
  12. 04 Mar, 2020 1 commit