1. 22 Apr, 2013 1 commit
  2. 19 Apr, 2013 1 commit
  3. 18 Apr, 2013 1 commit
    • antirez's avatar
      Redis/Jemalloc Gitignore were too aggressive. · 5bf9b53a
      antirez authored
      Redis gitignore was too aggressive since simply broken.
      
      Jemalloc gitignore was too agressive because it is conceived to just
      keep the files that allow to generate all the rest in development
      environments (so for instance the "configure" file is excluded).
      5bf9b53a
  4. 11 Apr, 2013 2 commits
    • antirez's avatar
      redis-cli: raise error on bad command line switch. · 40861516
      antirez authored
      Previously redis-cli never tried to raise an error when an unrecognized
      switch was encountered, as everything after the initial options is to be
      transmitted to the server.
      
      However this is too liberal, as there are no commands starting with "-".
      So the new behavior is to produce an error if there is an unrecognized
      switch starting with "-". This should not break past redis-cli usages
      but should prevent broken options to be silently discarded.
      
      As far the first token not starting with "-" is encountered, all the
      rest is considered to be part of the command, so you cna still use
      strings starting with "-" as values, like in:
      
          redis-cli --port 6380 set foo --my-value
      40861516
    • antirez's avatar
      redis-cli: --latency-history mode implemented. · 92a7b010
      antirez authored
      92a7b010
  5. 04 Apr, 2013 1 commit
  6. 03 Apr, 2013 1 commit
  7. 02 Apr, 2013 1 commit
    • antirez's avatar
      Throttle BGSAVE attempt on saving error. · ed2d9881
      antirez authored
      When a BGSAVE fails, Redis used to flood itself trying to BGSAVE at
      every next cron call, that is either 10 or 100 times per second
      depending on configuration and server version.
      
      This commit does not allow a new automatic BGSAVE attempt to be
      performed before a few seconds delay (currently 5).
      
      This avoids both the auto-flood problem and filling the disk with
      logs at a serious rate.
      
      The five seconds limit, considering a log entry of 200 bytes, will use
      less than 4 MB of disk space per day that is reasonable, the sysadmin
      should notice before of catastrofic events especially since by default
      Redis will stop serving write queries after the first failed BGSAVE.
      
      This fixes issue #849
      ed2d9881
  8. 29 Mar, 2013 2 commits
  9. 28 Mar, 2013 7 commits
  10. 27 Mar, 2013 8 commits
  11. 26 Mar, 2013 1 commit
  12. 25 Mar, 2013 3 commits
    • NanXiao's avatar
      Update config.c · ef1cf15c
      NanXiao authored
      Fix bug in configGetCommand function: get correct masterauth value.
      ef1cf15c
    • antirez's avatar
      Test: obuf-limits test false positive removed. · dee8d842
      antirez authored
      Fixes #621.
      dee8d842
    • antirez's avatar
      redis-cli --stat, stolen from redis-tools. · 5576a289
      antirez authored
      Redis-tools is a connection of tools no longer mantained that was
      intented as a way to economically make sense of Redis in the pre-vmware
      sponsorship era. However there was a nice redis-stat utility, this
      commit imports one of the functionalities of this tool here in redis-cli
      as it seems to be pretty useful.
      
      Usage: redis-cli --stat
      
      The output is similar to vmstat in the format, but with Redis specific
      stuff of course.
      
      From the point of view of the monitored instance, only INFO is used in
      order to grab data.
      5576a289
  13. 13 Mar, 2013 6 commits
  14. 12 Mar, 2013 3 commits
  15. 11 Mar, 2013 2 commits
    • antirez's avatar
      Redis 2.6.11 · 65898210
      antirez authored
      65898210
    • antirez's avatar
      activeExpireCycle() smarter with many DBs and under expire pressure. · 48f4f771
      antirez authored
      activeExpireCycle() tries to test just a few DBs per iteration so that
      it scales if there are many configured DBs in the Redis instance.
      However this commit makes it a bit smarter when one a few of those DBs
      are under expiration pressure and there are many many keys to expire.
      
      What we do is to remember if in the last iteration had to return because
      we ran out of time. In that case the next iteration we'll test all the
      configured DBs so that we are sure we'll test again the DB under
      pressure.
      
      Before of this commit after some mass-expire in a given DB the function
      tested just a few of the next DBs, possibly empty, a few per iteration,
      so it took a long time for the function to reach again the DB under
      pressure. This resulted in a lot of memory being used by already expired
      keys and never accessed by clients.
      48f4f771