1. 08 May, 2014 3 commits
    • antirez's avatar
      Sentinel: log when a failover will be attempted again. · 6eadeb72
      antirez authored
      When a Sentinel performs a failover (successful or not), or when a
      Sentinel votes for a different Sentinel trying to start a failover, it
      sets a min delay before it will try to get elected for a failover.
      
      While not strictly needed, because if multiple Sentinels will try
      to failover the same master at the same time, only one configuration
      will eventually win, this serialization is practically very useful.
      Normal failovers are cleaner: one Sentinel starts to failover, the
      others update their config when the Sentinel performing the failover
      is able to get the selected slave to move from the role of slave to the
      one of master.
      
      However currently this timeout was implicit, so users could see
      Sentinels not reacting, after a failed failover, for some time, without
      giving any feedback in the logs to the poor sysadmin waiting for clues.
      
      This commit makes Sentinels more verbose about the delay: when a master
      is down and a failover attempt is not performed because the delay has
      still not elaped, something like that will be logged:
      
          Next failover delay: I will not start a failover
          before Thu May  8 16:48:59 2014
      6eadeb72
    • antirez's avatar
      Sentinel: generate +config-update-from event when a new config is received. · c738f0f4
      antirez authored
      This event makes clear, before the switch-master event is generated,
      that a Sentinel received a configuration update from another Sentinel.
      c738f0f4
    • antirez's avatar
      REDIS_ENCODING_EMBSTR_SIZE_LIMIT set to 39. · d8ffd2b2
      antirez authored
      The new value is the limit for the robj + SDS header + string +
      null-term to stay inside the 64 bytes Jemalloc arena in 64 bits
      systems.
      d8ffd2b2
  2. 07 May, 2014 11 commits
  3. 05 May, 2014 17 commits
  4. 28 Apr, 2014 9 commits
    • antirez's avatar
      CLIENT LIST speedup via peerid caching + smart allocation. · a11ae385
      antirez authored
      This commit adds peer ID caching in the client structure plus an API
      change and the use of sdsMakeRoomFor() in order to improve the
      reallocation pattern to generate the CLIENT LIST output.
      
      Both the changes account for a very significant speedup.
      a11ae385
    • antirez's avatar
      bb00154f
    • antirez's avatar
      Added new sdscatfmt() %u and %U format specifiers. · e285a570
      antirez authored
      This commit also fixes a bug in the implementation of sdscatfmt()
      resulting from stale references to the SDS string header after
      sdsMakeRoomFor() calls.
      e285a570
    • antirez's avatar
      sdscatfmt() added to SDS library. · 0ab06bb5
      antirez authored
      sdscatprintf() relies on printf() family libc functions and is sometimes
      too slow in critical code paths. sdscatfmt() is an alternative which is:
      
      1) Far less capable.
      2) Format specifier uncompatible.
      3) Faster.
      
      It is suitable to be used in those speed critical code paths such as
      CLIENT LIST output generation.
      0ab06bb5
    • antirez's avatar
      Test: fixed scripting.tcl test false positive. · eeab60d1
      antirez authored
      eeab60d1
    • antirez's avatar
      Process events with processEventsWhileBlocked() when blocked. · cdd2bd56
      antirez authored
      When we are blocked and a few events a processed from time to time, it
      is smarter to call the event handler a few times in order to handle the
      accept, read, write, close cycle of a client in a single pass, otherwise
      there is too much latency added for clients to receive a reply while the
      server is busy in some way (for example during the DB loading).
      cdd2bd56
    • antirez's avatar
      Accept multiple clients per iteration. · 357b039f
      antirez authored
      When the listening sockets readable event is fired, we have the chance
      to accept multiple clients instead of accepting a single one. This makes
      Redis more responsive when there is a mass-connect event (for example
      after the server startup), and in workloads where a connect-disconnect
      pattern is used often, so that multiple clients are waiting to be
      accepted continuously.
      
      As a side effect, this commit makes the LOADING, BUSY, and similar
      errors much faster to deliver to the client, making Redis more
      responsive when there is to return errors to inform the clients that the
      server is blocked in an not interruptible operation.
      357b039f
    • antirez's avatar
      AE_ERR -> ANET_ERR in acceptUnixHandler(). · ba861194
      antirez authored
      No actual changes since the value is the same.
      ba861194
    • antirez's avatar
      Redis Cluster test framework skeleton. · a8464828
      antirez authored
      a8464828