1. 27 Feb, 2014 1 commit
    • antirez's avatar
      Initial implementation of BITPOS. · 38c620b3
      antirez authored
      It appears to work but more stress testing, and both unit tests and
      fuzzy testing, is needed in order to ensure the implementation is sane.
      38c620b3
  2. 21 Feb, 2014 1 commit
    • Matt Stancliff's avatar
      Add cluster or sentinel to proc title · 2c273e35
      Matt Stancliff authored
      If you launch redis with `redis-server --sentinel` then
      in a ps, your output only says "redis-server IP:Port" — this
      patch changes the proc title to include [sentinel] or
      [cluster] depending on the current server mode:
      e.g.  "redis-server IP:Port [sentinel]"
            "redis-server IP:Port [cluster]"
      2c273e35
  3. 17 Feb, 2014 1 commit
    • antirez's avatar
      Get absoulte config file path before processig 'dir'. · ede33fb9
      antirez authored
      The code tried to obtain the configuration file absolute path after
      processing the configuration file. However if config file was a relative
      path and a "dir" statement was processed reading the config, the absolute
      path obtained was wrong.
      
      With this fix the absolute path is obtained before processing the
      configuration while the server is still in the original directory where
      it was executed.
      ede33fb9
  4. 13 Feb, 2014 1 commit
    • antirez's avatar
      Update cached time in rdbLoad() callback. · 51bd9da1
      antirez authored
      server.unixtime and server.mstime are cached less precise timestamps
      that we use every time we don't need an accurate time representation and
      a syscall would be too slow for the number of calls we require.
      
      Such an example is the initialization and update process of the last
      interaction time with the client, that is used for timeouts.
      
      However rdbLoad() can take some time to load the DB, but at the same
      time it did not updated the time during DB loading. This resulted in the
      bug described in issue #1535, where in the replication process the slave
      loads the DB, creates the redisClient representation of its master, but
      the timestamp is so old that the master, under certain conditions, is
      sensed as already "timed out".
      
      Thanks to @yoav-steinberg and Redis Labs Inc for the bug report and
      analysis.
      51bd9da1
  5. 12 Feb, 2014 2 commits
    • antirez's avatar
      AOF write error: retry with a frequency of 1 hz. · fc08c859
      antirez authored
      fc08c859
    • antirez's avatar
      AOF: don't abort on write errors unless fsync is 'always'. · fe835254
      antirez authored
      A system similar to the RDB write error handling is used, in which when
      we can't write to the AOF file, writes are no longer accepted until we
      are able to write again.
      
      For fsync == always we still abort on errors since there is currently no
      easy way to avoid replying with success to the user otherwise, and this
      would violate the contract with the user of only acknowledging data
      already secured on disk.
      fe835254
  6. 07 Feb, 2014 2 commits
  7. 04 Feb, 2014 1 commit
    • antirez's avatar
      CLIENT PAUSE and related API implemented. · 4919a13f
      antirez authored
      The API is one of the bulding blocks of CLUSTER FAILOVER command that
      executes a manual failover in Redis Cluster. However exposed as a
      command that the user can call directly, it makes much simpler to
      upgrade a standalone Redis instance using a slave in a safer way.
      
      The commands works like that:
      
          CLIENT PAUSE <milliesconds>
      
      All the clients that are not slaves and not in MONITOR state are paused
      for the specified number of milliesconds. This means that slaves are
      normally served in the meantime.
      
      At the end of the specified amount of time all the clients are unblocked
      and will continue operations normally. This command has no effects on
      the population of the slow log, since clients are not blocked in the
      middle of operations but only when there is to process new data.
      
      Note that while the clients are unblocked, still new commands are
      accepted and queued in the client buffer, so clients will likely not
      block while writing to the server while the pause is active.
      4919a13f
  8. 03 Feb, 2014 1 commit
  9. 31 Jan, 2014 3 commits
  10. 28 Jan, 2014 1 commit
  11. 14 Jan, 2014 1 commit
    • antirez's avatar
      Cluster: support to read from slave nodes. · 28273394
      antirez authored
      A client can enter a special cluster read-only mode using the READONLY
      command: if the client read from a slave instance after this command,
      for slots that are actually served by the instance's master, the queries
      will be processed without redirection, allowing clients to read from
      slaves (but without any kind fo read-after-write guarantee).
      
      The READWRITE command can be used in order to exit the readonly state.
      28273394
  12. 23 Dec, 2013 1 commit
  13. 19 Dec, 2013 1 commit
  14. 11 Dec, 2013 1 commit
    • antirez's avatar
      Replication: publish the slave_repl_offset when disconnected from master. · a5ec247f
      antirez authored
      When a slave was disconnected from its master the replication offset was
      reported as -1. Now it is reported as the replication offset of the
      previous master, so that failover can be performed using this value in
      order to try to select a slave with more processed data from a set of
      slaves of the old master.
      a5ec247f
  15. 05 Dec, 2013 2 commits
  16. 04 Dec, 2013 1 commit
  17. 03 Dec, 2013 1 commit
  18. 29 Nov, 2013 1 commit
  19. 28 Nov, 2013 2 commits
  20. 21 Nov, 2013 1 commit
  21. 19 Nov, 2013 1 commit
    • antirez's avatar
      Sentinel: distinguish between is-master-down-by-addr requests. · 37a51a25
      antirez authored
      Some are just to know if the master is down, and in this case the runid
      in the request is set to "*", others are actually in order to seek for a
      vote and get elected. In the latter case the runid is set to the runid
      of the instance seeking for the vote.
      37a51a25
  22. 28 Oct, 2013 4 commits
  23. 25 Oct, 2013 2 commits
  24. 09 Oct, 2013 2 commits
  25. 26 Sep, 2013 1 commit
  26. 17 Sep, 2013 1 commit
  27. 27 Aug, 2013 1 commit
  28. 22 Aug, 2013 2 commits