1. 23 Jun, 2016 2 commits
    • antirez's avatar
      Commit change in autoMemoryFreed(): first -> last. · b5072897
      antirez authored
      It's more natural to call the last entry added as "last", the original
      commet got me confused until I actually read the code.
      b5072897
    • antirez's avatar
      Modules: implement zig-zag scanning in autoMemoryFreed(). · f2dbc02f
      antirez authored
      Most of the time to check the last element is the way to go, however
      there are patterns where the contrary is the best choice. Zig-zag
      scanning implemented in this commmit always checks the obvious element
      first (the last added -- think at a loop where the last element
      allocated gets freed again and again), and continues checking one
      element in the head and one in the tail.
      
      Thanks to @dvisrky that fixed the original implementation of the
      function and proposed zig zag scanning.
      f2dbc02f
  2. 22 Jun, 2016 1 commit
  3. 16 Jun, 2016 4 commits
    • antirez's avatar
      Fix Sentinel pending commands counting. · f7351f4c
      antirez authored
      This bug most experienced effect was an inability of Redis to
      reconfigure back old masters to slaves after they are reachable again
      after a failover. This was due to failing to reset the count of the
      pending commands properly, so the master appeared fovever down.
      
      Was introduced in Redis 3.2 new Sentinel connection sharing feature
      which is a lot more complex than the 3.0 code, but more scalable.
      
      Many thanks to people reporting the issue, and especially to
      @sskorgal for investigating the issue in depth.
      
      Hopefully closes #3285.
      f7351f4c
    • antirez's avatar
      redis-cli: really connect to the right server. · 7c8f275a
      antirez authored
      I recently introduced populating the autocomplete help array with the
      COMMAND command if available. However this was performed before parsing
      the arguments, defaulting to instance 6379. After the connection is
      performed it remains stable.
      
      The effect is that if there is an instance running on port 6339,
      whatever port you specify is ignored and 6379 is connected to instead.
      The right port will be selected only after a reconnection.
      
      Close #3314.
      7c8f275a
    • antirez's avatar
      RESTORE: accept RDB dumps with older versions. · a3f893b8
      antirez authored
      Reference issue #3218.
      
      Checking the code I can't find a reason why the original RESTORE
      code was so opinionated about restoring only the current version. The
      code in to `rdb.c` appears to be capable as always to restore data from
      older versions of Redis, and the only places where it is needed the
      current version in order to correctly restore data, is while loading the
      opcodes, not the values itself as it happens in the case of RESTORE.
      
      For the above reasons, this commit enables RESTORE to accept older
      versions of values payloads.
      a3f893b8
    • antirez's avatar
      Minor aesthetic fixes to PR #3264. · 2f2fd64c
      antirez authored
      Comment format fixed + local var modified from camel case to underscore
      separators as Redis code base normally does (camel case is mostly used
      for global symbols like structure names, function names, global vars,
      ...).
      2f2fd64c
  4. 15 Jun, 2016 2 commits
  5. 14 Jun, 2016 3 commits
  6. 13 Jun, 2016 6 commits
  7. 10 Jun, 2016 5 commits
  8. 08 Jun, 2016 1 commit
  9. 07 Jun, 2016 2 commits
  10. 05 Jun, 2016 7 commits
  11. 04 Jun, 2016 2 commits
  12. 03 Jun, 2016 3 commits
  13. 01 Jun, 2016 2 commits