1. 24 Jul, 2019 1 commit
  2. 23 Jul, 2019 3 commits
  3. 22 Jul, 2019 1 commit
  4. 10 Jul, 2019 1 commit
  5. 08 Jul, 2019 1 commit
    • Oran Agra's avatar
      diskless replication on slave side (don't store rdb to file), plus some other related fixes · 2de544cf
      Oran Agra authored
      The implementation of the diskless replication was currently diskless only on the master side.
      The slave side was still storing the received rdb file to the disk before loading it back in and parsing it.
      
      This commit adds two modes to load rdb directly from socket:
      1) when-empty
      2) using "swapdb"
      the third mode of using diskless slave by flushdb is risky and currently not included.
      
      other changes:
      --------------
      distinguish between aof configuration and state so that we can re-enable aof only when sync eventually
      succeeds (and not when exiting from readSyncBulkPayload after a failed attempt)
      also a CONFIG GET and INFO during rdb loading would have lied
      
      When loading rdb from the network, don't kill the server on short read (that can be a network error)
      
      Fix rdb check when performed on preamble AOF
      
      tests:
      run replication tests for diskless slave too
      make replication test a bit more aggressive
      Add test for diskless load swapdb
      2de544cf
  6. 03 Jul, 2019 1 commit
  7. 07 Jun, 2019 1 commit
  8. 06 May, 2019 9 commits
  9. 20 Mar, 2019 1 commit
  10. 18 Mar, 2019 1 commit
  11. 03 Mar, 2019 1 commit
  12. 27 Feb, 2019 1 commit
  13. 25 Feb, 2019 1 commit
  14. 21 Feb, 2019 1 commit
  15. 13 Feb, 2019 2 commits
    • zhaozhao.zz's avatar
      ACL: show categories in COMMAND reply · 14507457
      zhaozhao.zz authored
      Adding another new filed categories at the end of
      command reply, it's easy to read and distinguish
      flags and categories, also compatible with old format.
      14507457
    • antirez's avatar
      ACL: tag LASTSAVE as dangerous. · e819c2ef
      antirez authored
      That's not REALLY needed, but... right now with LASTSAVE being the only
      command tagged as "admin" but not "dangerous" what happens is that after
      rewrites the rewrite engine will produce from the rules:
      
          user default on +@all ~* -@dangerous nopass
      
      The rewrite:
      
          user default on nopass ~* +@all -@admin -@dangerous +lastsave
      
      Which is correct but will have users wondering about why LASTSAVE has
      something special.
      
      Since LASTSAVE after all also leaks information about the underlying
      server configuration, that may not be great for SAAS vendors, let's tag
      it as dangerous as well and forget about this issue :-)
      e819c2ef
  16. 12 Feb, 2019 1 commit
  17. 11 Feb, 2019 1 commit
  18. 07 Feb, 2019 1 commit
  19. 05 Feb, 2019 1 commit
  20. 04 Feb, 2019 1 commit
  21. 23 Jan, 2019 4 commits
  22. 22 Jan, 2019 4 commits
  23. 21 Jan, 2019 1 commit