1. 31 Oct, 2018 4 commits
    • antirez's avatar
      Add support for Sentinel authentication. · fa675256
      antirez authored
      So far it was not possible to setup Sentinel with authentication
      enabled. This commit introduces this feature: every Sentinel will try to
      authenticate with other sentinels using the same password it is
      configured to accept clients with.
      
      So for instance if a Sentinel has a "requirepass" configuration
      statemnet set to "foo", it will use the "foo" password to authenticate
      with every other Sentinel it connects to. So basically to add the
      "requirepass" to all the Sentinels configurations is enough in order to
      make sure that:
      
      1) Clients will require the password to access the Sentinels instances.
      2) Each Sentinel will use the same password to connect and authenticate
         with every other Sentinel in the group.
      
      Related to #3279 and #3329.
      fa675256
    • antirez's avatar
      Disable protected mode in Sentinel mode. · 666b3437
      antirez authored
      Sentinel must be exposed, so protected mode is just an issue for users
      in case Redis was started in Sentinel mode.
      
      Related to #3279 and #3329.
      666b3437
    • antirez's avatar
      When replica kills a pending RDB save during SYNC, log it. · 06a4acb7
      antirez authored
      This logs what happens in the context of the fix in PR #5367.
      06a4acb7
    • Salvatore Sanfilippo's avatar
      Merge pull request #5367 from nUl1/fullresync-stopbgsave · 6204d8c1
      Salvatore Sanfilippo authored
      Prevent RDB autosave from overwriting full resync results
      6204d8c1
  2. 30 Oct, 2018 1 commit
    • antirez's avatar
      asyncCloseClientOnOutputBufferLimitReached(): don't free fake clients. · 0c875c77
      antirez authored
      Fake clients are used in special situations and are not linked to the
      normal clients list, freeing them will always result in Redis crashing
      in one way or the other.
      
      It's not common to send replies to fake clients, but we have one usage
      in the modules API. When a client is blocked, we associate to the
      blocked client object (that is safe to manipulate in a thread), a fake
      client that accumulates replies. So because of this bug there was
      the problem described in issue #5443.
      
      The fix was verified to work with the provided example module. To write
      a regression is very hard and unlikely to be triggered in the future.
      0c875c77
  3. 29 Oct, 2018 1 commit
  4. 26 Oct, 2018 2 commits
  5. 25 Oct, 2018 6 commits
  6. 24 Oct, 2018 5 commits
  7. 22 Oct, 2018 5 commits
  8. 21 Oct, 2018 1 commit
  9. 20 Oct, 2018 1 commit
  10. 19 Oct, 2018 3 commits
  11. 18 Oct, 2018 1 commit
  12. 17 Oct, 2018 10 commits