1. 14 Jun, 2017 1 commit
  2. 13 Jun, 2017 3 commits
  3. 04 Jun, 2017 2 commits
  4. 19 May, 2017 2 commits
  5. 15 May, 2017 1 commit
  6. 10 May, 2017 3 commits
    • antirez's avatar
    • antirez's avatar
      Modules TSC: use atomic var for server.unixtime. · 1f598fc2
      antirez authored
      This avoids Helgrind complaining, but we are actually not using
      atomicGet() to get the unixtime value for now: too many places where it
      is used and given tha time_t is word-sized it should be safe in all the
      archs we support as it is.
      
      On the other hand, Helgrind, when Redis is compiled with "make helgrind"
      in order to force the __sync macros, will detect the write in
      updateCachedTime() as a read (because atomic functions are used) and
      will not complain about races.
      
      This commit also includes minor refactoring of mutex initializations and
      a "helgrind" target in the Makefile.
      1f598fc2
    • antirez's avatar
      atomicvar.h: show used API in INFO. Add macro to force __sync builtin. · de786186
      antirez authored
      The __sync builtin can be correctly detected by Helgrind so to force it
      is useful for testing. The API in the INFO output can be useful for
      debugging after problems are reported.
      de786186
  7. 09 May, 2017 3 commits
  8. 04 May, 2017 2 commits
  9. 03 May, 2017 8 commits
  10. 02 May, 2017 3 commits
  11. 28 Apr, 2017 3 commits
  12. 27 Apr, 2017 1 commit
    • antirez's avatar
      PSYNC2: fix master cleanup when caching it. · 469d6e2b
      antirez authored
      The master client cleanup was incomplete: resetClient() was missing and
      the output buffer of the client was not reset, so pending commands
      related to the previous connection could be still sent.
      
      The first problem caused the client argument vector to be, at times,
      half populated, so that when the correct replication stream arrived the
      protcol got mixed to the arugments creating invalid commands that nobody
      called.
      
      Thanks to @yangsiran for also investigating this problem, after
      already providing important design / implementation hints for the
      original PSYNC2 issues (see referenced Github issue).
      
      Note that this commit adds a new function to the list library of Redis
      in order to be able to reset a list without destroying it.
      
      Related to issue #3899.
      469d6e2b
  13. 22 Apr, 2017 4 commits
  14. 21 Apr, 2017 1 commit
    • antirez's avatar
      Check event loop creation return value. Fix #3951. · 238cebdd
      antirez authored
      Normally we never check for OOM conditions inside Redis since the
      allocator will always return a pointer or abort the program on OOM
      conditons. However we cannot have control on epool_create(), that may
      fail for kernel OOM (according to the manual page) even if all the
      parameters are correct, so the function aeCreateEventLoop() may indeed
      return NULL and this condition must be checked.
      238cebdd
  15. 20 Apr, 2017 1 commit
  16. 19 Apr, 2017 2 commits
    • antirez's avatar
      Fix getKeysUsingCommandTable() in cluster mode. · 7d9dd80d
      antirez authored
      Close #3940.
      7d9dd80d
    • antirez's avatar
      PSYNC2: discard pending transactions from cached master. · 189a12af
      antirez authored
      During the review of the fix for #3899, @yangsiran identified an
      implementation bug: given that the offset is now relative to the applied
      part of the replication log, when we cache a master, the successive
      PSYNC2 request will be made in order to *include* the transaction that
      was not completely processed. This means that we need to discard any
      pending transaction from our replication buffer: it will be re-executed.
      189a12af