1. 07 Dec, 2018 1 commit
  2. 23 Nov, 2018 2 commits
    • Chris Lamb's avatar
      Don't treat unsupported protocols as fatal errors · fbff3514
      Chris Lamb authored
      If we encounter an unsupported protocol in the "bind" list, don't
      ipso-facto consider it a fatal error. We continue to abort startup if
      there are no listening sockets at all.
      
      This ensures that the lack of IPv6 support does not prevent Redis from
      starting on Debian where we try to bind to the ::1 interface by default
      (via "bind 127.0.0.1 ::1"). A machine with IPv6 disabled (such as some
      container systems) would simply fail to start Redis after the initiall
      call to apt(8).
      
      This is similar to the case for where "bind" is not specified:
      
        https://github.com/antirez/redis/issues/3894
      
      ... and was based on the corresponding PR:
      
        https://github.com/antirez/redis/pull/4108
      
      ... but also adds EADDRNOTAVAIL to the list of errors to catch which I
      believe is missing from there.
      
      This issue was raised in Debian as both <https://bugs.debian.org/900284>
      & <https://bugs.debian.org/914354>.
      fbff3514
    • Chris Lamb's avatar
      Clarify the "Creating Server TCP listening socket" error. · 9cfcf379
      Chris Lamb authored
      This really helps spot it in the logs, otherwise it does not look like a
      warning/error. For example:
      
        Creating Server TCP listening socket ::1:6379: bind: Cannot assign requested address
      
      ... is not nearly as clear as:
      
        Could not create server TCP listening listening socket ::1:6379: bind: Cannot assign requested address
      9cfcf379
  3. 05 Nov, 2018 1 commit
    • valentino's avatar
      fix short period of server.hz being uninitialized · eae8d058
      valentino authored
      server.hz was uninitialized between initServerConfig and initServer.
      this can lead to someone (e.g. queued modules) doing createObject,
      and accessing an uninitialized variable, that can potentially be 0,
      and lead to a crash.
      eae8d058
  4. 26 Oct, 2018 1 commit
    • David Carlier's avatar
      Fix non Linux build. · 0b73d0a8
      David Carlier authored
      timezone global is a linux-ism whereas it is a function under BSD.
      Here a helper to get the timezone value in a more portable manner.
      0b73d0a8
  5. 17 Oct, 2018 1 commit
  6. 16 Oct, 2018 1 commit
  7. 10 Oct, 2018 1 commit
  8. 09 Oct, 2018 1 commit
  9. 02 Oct, 2018 1 commit
  10. 30 Sep, 2018 2 commits
    • Bruce Merry's avatar
      Fix incorrect memory usage accounting in zrealloc · 8fd1031b
      Bruce Merry authored
      When HAVE_MALLOC_SIZE is false, each call to zrealloc causes used_memory
      to increase by PREFIX_SIZE more than it should, due to mis-matched
      accounting between the original zmalloc (which includes PREFIX size in
      its increment) and zrealloc (which misses it from its decrement).
      
      I've also supplied a command-line test to easily demonstrate the
      problem. It's not wired into the test framework, because I don't know
      TCL so I'm not sure how to automate it.
      8fd1031b
    • Oran Agra's avatar
      fix #5024 - commandstats for multi-exec were logged as EXEC. · f03aed3c
      Oran Agra authored
      this was broken a while back by ba9154d7
      the purpose of which was to fix commandstats for GEOADD
      f03aed3c
  11. 19 Sep, 2018 2 commits
  12. 12 Sep, 2018 1 commit
  13. 11 Sep, 2018 2 commits
  14. 06 Sep, 2018 1 commit
    • zhaozhao.zz's avatar
      Scripting & Streams: some commands need right flags · 8d24f8b4
      zhaozhao.zz authored
      xadd with id * generates random stream id
      
      xadd & xtrim with approximate maxlen count may
      trim stream randomly
      
      xinfo may get random radix-tree-keys/nodes
      
      xpending may get random idletime
      
      xclaim: master and slave may have different
      idletime in stream
      8d24f8b4
  15. 05 Sep, 2018 3 commits
  16. 31 Aug, 2018 2 commits
    • antirez's avatar
      While the slave is busy, just accumulate master input. · 9ab91b8c
      antirez authored
      Processing command from the master while the slave is in busy state is
      not correct, however we cannot, also, just reply -BUSY to the
      replication stream commands from the master. The correct solution is to
      stop processing data from the master, but just accumulate the stream
      into the buffers and resume the processing later.
      
      Related to #5297.
      9ab91b8c
    • antirez's avatar
      Allow scripts to timeout on slaves as well. · f5b29c64
      antirez authored
      See reasoning in #5297.
      f5b29c64
  17. 29 Aug, 2018 2 commits
  18. 27 Aug, 2018 2 commits
  19. 14 Aug, 2018 1 commit
  20. 13 Aug, 2018 1 commit
  21. 03 Aug, 2018 1 commit
  22. 31 Jul, 2018 4 commits
  23. 30 Jul, 2018 3 commits
  24. 23 Jul, 2018 2 commits
  25. 20 Jul, 2018 1 commit