1. 20 Aug, 2015 3 commits
  2. 07 Aug, 2015 2 commits
  3. 06 Aug, 2015 2 commits
    • antirez's avatar
      809e2f4d
    • antirez's avatar
      Replication: add REPLCONF CAPA EOF support. · ba323760
      antirez authored
      Add the concept of slaves capabilities to Redis, the slave now presents
      to the Redis master with a set of capabilities in the form:
      
          REPLCONF capa SOMECAPA capa OTHERCAPA ...
      
      This has the effect of setting slave->slave_capa with the corresponding
      SLAVE_CAPA macros that the master can test later to understand if it
      the slave will understand certain formats and protocols of the
      replication process. This makes it much simpler to introduce new
      replication capabilities in the future in a way that don't break old
      slaves or masters.
      
      This patch was designed and implemented together with Oran Agra
      (@oranagra).
      ba323760
  4. 05 Aug, 2015 11 commits
    • antirez's avatar
      Fix synchronous readline "\n" handling. · ade9bf7c
      antirez authored
      Our function to read a line with a timeout handles newlines as requests
      to refresh the timeout, however the code kept subtracting the buffer
      size left every time a newline was received, for a bug in the loop
      logic. Fixed by this commit.
      ade9bf7c
    • antirez's avatar
      Fix replication slave pings period. · 64b28d10
      antirez authored
      For PINGs we use the period configured by the user, but for the newlines
      of slaves waiting for an RDB to be created (including slaves waiting for
      the FULLRESYNC reply) we need to ping with frequency of 1 second, since
      the timeout is fixed and needs to be refreshed.
      64b28d10
    • antirez's avatar
      Fix RDB encoding test for new csvdump format. · dcc5ee15
      antirez authored
      dcc5ee15
    • antirez's avatar
    • antirez's avatar
      Make sure we re-emit SELECT after each new slave full sync setup. · 27c0ab23
      antirez authored
      In previous commits we moved the FULLRESYNC to the moment we start the
      BGSAVE, so that the offset we provide is the right one. However this
      also means that we need to re-emit the SELECT statement every time a new
      slave starts to accumulate the changes.
      
      To obtian this effect in a more clean way, the function that sends the
      FULLRESYNC reply was overloaded with a more important role of also doing
      this and chanigng the slave state. So it was renamed to
      replicationSetupSlaveForFullResync() to better reflect what it does now.
      27c0ab23
    • antirez's avatar
      Test: csvdump now scans all DBs. · 547ccc4b
      antirez authored
      547ccc4b
    • antirez's avatar
      99e4cf4d
    • antirez's avatar
      PSYNC test: also test the vanilla SYNC. · 1dccb6cf
      antirez authored
      1dccb6cf
    • antirez's avatar
      syncCommand() comments improved. · f6c65d3f
      antirez authored
      f6c65d3f
    • antirez's avatar
      PSYNC initial offset fix. · 9d297218
      antirez authored
      This commit attempts to fix a bug involving PSYNC and diskless
      replication (currently experimental) found by Yuval Inbar from Redis Labs
      and that was later found to have even more far reaching effects (the bug also
      exists when diskstore is off).
      
      The gist of the bug is that, a Redis master replies with +FULLRESYNC to
      a PSYNC attempt that fails and requires a full resynchronization.
      However, the baseline offset sent along with FULLRESYNC was always the
      current master replication offset. This is not ok, because there are
      many reasosn that may delay the RDB file creation. And... guess what,
      the master offset we communicate must be the one of the time the RDB
      was created. So for example:
      
      1) When the BGSAVE for replication is delayed since there is one
         already but is not good for replication.
      2) When the BGSAVE is not needed as we attach one currently ongoing.
      3) When because of diskless replication the BGSAVE is delayed.
      
      In all the above cases the PSYNC reply is wrong and the slave may
      reconnect later claiming to need a wrong offset: this may cause
      data curruption later.
      9d297218
    • antirez's avatar
      Test PSYNC with diskless replication. · 32e97980
      antirez authored
      Thanks to Oran Agra from Redis Labs for providing this patch.
      32e97980
  5. 17 Jul, 2015 5 commits
  6. 16 Jul, 2015 2 commits
    • antirez's avatar
      Client timeout handling improved. · b029ff11
      antirez authored
      The previos attempt to process each client at least once every ten
      seconds was not a good idea, because:
      
      1. Usually because of the past min iterations set to 50, you get much
      better processing period most of the times.
      
      2. However when there are many clients and a normal setting for
      server.hz, the edge case is triggered, and waiting 10 seconds for a
      BLPOP that asked for 1 second is not ok.
      
      3. Moreover, because of the high min-itereations limit of 50, when HZ
      was set to an high value, the actual behavior was to process a lot of
      clients per second.
      
      Also the function checking for timeouts called gettimeofday() at each
      iteration which can be costly.
      
      The new implementation will try to process each client once per second,
      gets the current time as argument, and does not attempt to process more
      than 5 clients per iteration if not needed.
      
      So now:
      
      1. The CPU usage of an idle Redis process is the same or better.
      2. The CPU usage of a busy Redis process is the same or better.
      3. However a non trivial amount of work may be performed per iteration
      when there are many many clients. In this particular case the user may
      want to raise the "HZ" value if needed.
      
      Btw with 4000 clients it was still not possible to noticy any actual
      latency created by processing 400 clients per second, since the work
      performed for each client is pretty small.
      b029ff11
    • antirez's avatar
      Clarify a comment in clientsCron(). · 5dcba26b
      antirez authored
      5dcba26b
  7. 13 Jul, 2015 1 commit
    • antirez's avatar
      EXISTS is now variadic. · 7ae1d4d6
      antirez authored
      The new return value is the number of keys existing, among the ones
      specified in the command line, counting the same key multiple times if
      given multiple times (and if it exists).
      
      See PR #2667.
      7ae1d4d6
  8. 29 Jun, 2015 1 commit
  9. 11 Jun, 2015 5 commits
    • linfangrong's avatar
      Update t_zset.c · d4a7c9e1
      linfangrong authored
      d4a7c9e1
    • antirez's avatar
      Use best effort address binding to connect to the master · 4e8759c6
      antirez authored
      We usually want to reach the master using the address of the interface
      Redis is bound to (via the "bind" config option). That's useful since
      the master will get (and publish) the slave address getting the peer
      name of the incoming socket connection from the slave.
      
      However, when this is not possible, for example because the slave is
      bound to the loopback interface but repliaces from a master accessed via
      an external interface, we want to still connect with the master even
      from a different interface: in this case it is not really important that
      the master will provide any other address, while it is vital to be able
      to replicate correctly.
      
      Related to issues #2609 and #2612.
      4e8759c6
    • antirez's avatar
      anet.c: new API anetTcpNonBlockBestEffortBindConnect() · a8d7f00e
      antirez authored
      This performs a best effort source address binding attempt. If it is
      possible to bind the local address and still have a successful
      connect(), then this socket is returned. Otherwise the call is retried
      without source address binding attempt.
      
      Related to issues #2609 and #2612.
      a8d7f00e
    • antirez's avatar
      anetTcpGenericConnect(), jump to error not end on error · af8a9de6
      antirez authored
      Two code paths jumped to the "ok, return the socket to the user" code
      path to handle error conditions.
      
      Related to issues #2609 and #2612.
      af8a9de6
    • antirez's avatar
      Don't try to bind the source address for MIGRATE · d815289d
      antirez authored
      Related to issues #2609 and #2612.
      d815289d
  10. 04 Jun, 2015 2 commits
  11. 03 Jun, 2015 3 commits
  12. 29 May, 2015 3 commits