1. 06 May, 2019 1 commit
    • antirez's avatar
      Threaded IO: implement handleClientsWithPendingWritesUsingThreads(). · f468e653
      antirez authored
      This is just an experiment for now, there are a couple of race
      conditions, mostly harmless for the performance gain experiment that
      this commit represents so far.
      
      The general idea here is to take Redis single threaded and instead
      fan-out on expansive kernel calls: write(2) in this case, but the same
      concept could be easily implemented for read(2) and protcol parsing.
      
      However just threading writes like in this commit, is enough to evaluate
      if the approach is sounding.
      f468e653
  2. 24 Mar, 2019 1 commit
  3. 21 Mar, 2019 2 commits
  4. 18 Mar, 2019 1 commit
  5. 15 Mar, 2019 1 commit
  6. 07 Mar, 2019 1 commit
  7. 27 Feb, 2019 2 commits
  8. 25 Feb, 2019 1 commit
  9. 21 Feb, 2019 2 commits
  10. 13 Feb, 2019 1 commit
    • 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
  11. 12 Feb, 2019 2 commits
    • Guy Benoish's avatar
      Trim SDS free space of retained module strings · bdd9a800
      Guy Benoish authored
      In some cases processMultibulkBuffer uses sdsMakeRoomFor to
      expand the querybuf, but later in some cases it uses that query
      buffer as is for an argv element (see "Optimization"), which means
      that the sds in argv may have a lot of wasted space, and then in case
      modules keep that argv RedisString inside their data structure, this
      space waste will remain for long (until restarted from rdb).
      bdd9a800
    • zhaozhao.zz's avatar
      ACL: add masteruser configuration for replication · ea9d3aef
      zhaozhao.zz authored
      In mostly production environment, normal user's behavior should be
      limited.
      
      Now in redis ACL mechanism we can do it like that:
      
          user default on +@all ~* -@dangerous nopass
          user admin on +@all ~* >someSeriousPassword
      
      Then the default normal user can not execute dangerous commands like
      FLUSHALL/KEYS.
      
      But some admin commands are in dangerous category too like PSYNC,
      and the configurations above will forbid replica from sync with master.
      
      Finally I think we could add a new configuration for replication,
      it is masteruser option, like this:
      
          masteruser admin
          masterauth someSeriousPassword
      
      Then replica will try AUTH admin someSeriousPassword and get privilege
      to execute PSYNC. If masteruser is NULL, replica would AUTH with only
      masterauth like before.
      ea9d3aef
  12. 07 Feb, 2019 1 commit
  13. 05 Feb, 2019 1 commit
  14. 04 Feb, 2019 4 commits
  15. 31 Jan, 2019 1 commit
  16. 23 Jan, 2019 3 commits
  17. 22 Jan, 2019 1 commit
  18. 21 Jan, 2019 1 commit
  19. 18 Jan, 2019 1 commit
  20. 17 Jan, 2019 1 commit
  21. 16 Jan, 2019 1 commit
  22. 15 Jan, 2019 3 commits
  23. 14 Jan, 2019 3 commits
  24. 11 Jan, 2019 1 commit
  25. 10 Jan, 2019 3 commits