1. 29 Apr, 2015 1 commit
    • antirez's avatar
      A way to disable time accounting in call(). · da58926a
      antirez authored
      This commit allows to avoid two mstime() calls inside the call()
      function, when the following conditions are true:
      
      1. slowlog is disabled.
      2. latency monitoring is disabled.
      3. command time acconuting is disabled.
      
      Note that '3' was not configurable, this patch just disable it without
      really allowing the user to turn it on, since this is currently an
      experiment. If the commit will be merged into unstable, proper support
      to configure this parameter will be added.
      
      Related to issue #2552.
      da58926a
  2. 23 Dec, 2014 1 commit
    • antirez's avatar
      INFO loading stats: three fixes. · 22a0fe8d
      antirez authored
      1. Server unxtime may remain not updated while loading AOF, so ETA is
      not updated correctly.
      
      2. Number of processed byte was not initialized.
      
      3. Possible division by zero condition (likely cause of issue #1932).
      22a0fe8d
  3. 19 Dec, 2014 1 commit
  4. 13 Dec, 2014 2 commits
  5. 04 Dec, 2014 1 commit
  6. 03 Dec, 2014 2 commits
  7. 02 Dec, 2014 1 commit
    • antirez's avatar
      Mark PFCOUNT as read-only, even if not true. · 0e40124d
      antirez authored
      PFCOUNT is technically speaking a write command, since the cached value
      of the HLL is exposed in the data structure (design error, mea culpa), and
      can be modified by PFCOUNT.
      
      However if we flag PFCOUNT as "w", read only slaves can't execute the
      command, which is a problem since there are environments where slaves
      are used to scale PFCOUNT reads.
      
      Nor it is possible to just prevent PFCOUNT to modify the data structure
      in slaves, since without the cache we lose too much efficiency.
      
      So while this commit allows slaves to create a temporary inconsistency
      (the strings representing the HLLs in the master and slave can be
      different in certain moments) it is actually harmless.
      
      In the long run this should be probably fixed by turning the HLL into a
      more opaque representation, for example by storing the cached value in
      the part of the string which is not exposed (this should be possible
      with SDS strings).
      0e40124d
  8. 12 Nov, 2014 1 commit
  9. 29 Oct, 2014 5 commits
  10. 06 Oct, 2014 2 commits
  11. 16 Sep, 2014 1 commit
    • antirez's avatar
      Don't propagate SAVE. · fbd9dc60
      antirez authored
      This is a general fix (check that dirty delta is positive) but actually
      should have as the only effect fixing the SAVE propagation to
      AOF and slaves.
      fbd9dc60
  12. 08 Sep, 2014 1 commit
  13. 27 Aug, 2014 9 commits
  14. 18 Jul, 2014 3 commits
    • antirez's avatar
      06e9b3ca
    • antirez's avatar
      Variadic PING with support for Pub/Sub. · 70e39481
      antirez authored
      PING can now be called with an additional arugment, behaving exactly
      like the ECHO command. PING can now also be called in Pub/Sub mode (with
      one more more subscriptions to channels / patterns) in order to trigger
      the delivery of an asynchronous pong message with the optional payload.
      
      This fixes issue #420.
      70e39481
    • antirez's avatar
      PubSub clients refactoring and new PUBSUB flag. · 294bcfc4
      antirez authored
      The code tested many times if a client had active Pub/Sub subscriptions
      by checking the length of a list and dictionary where the patterns and
      channels are stored. This was substituted with a client flag called
      REDIS_PUBSUB that is simpler to test for. Moreover in order to manage
      this flag some code was refactored.
      
      This commit is believed to have no effects in the behavior of the
      server.
      294bcfc4
  15. 14 Jul, 2014 1 commit
    • michael-grunder's avatar
      Fix OBJECT arity · 3df2ab67
      michael-grunder authored
      Previously, the command definition for the OBJECT command specified
      a minimum of two args (and that it was variadic), which meant that
      if you sent this:
      
      OBJECT foo
      
      When cluster was enabled, it would result in an assertion/SEGFAULT
      when Redis was attempting to extract keys.
      
      It appears that OBJECT is not variadic, and only ever takes 3 args.
      
      https://gist.github.com/michael-grunder/25960ce1508396d0d36a
      3df2ab67
  16. 09 Jul, 2014 6 commits
  17. 02 Jul, 2014 1 commit
  18. 27 Jun, 2014 1 commit