1. 08 Jul, 2019 1 commit
    • Oran Agra's avatar
      diskless replication on slave side (don't store rdb to file), plus some other related fixes · 2de544cf
      Oran Agra authored
      The implementation of the diskless replication was currently diskless only on the master side.
      The slave side was still storing the received rdb file to the disk before loading it back in and parsing it.
      
      This commit adds two modes to load rdb directly from socket:
      1) when-empty
      2) using "swapdb"
      the third mode of using diskless slave by flushdb is risky and currently not included.
      
      other changes:
      --------------
      distinguish between aof configuration and state so that we can re-enable aof only when sync eventually
      succeeds (and not when exiting from readSyncBulkPayload after a failed attempt)
      also a CONFIG GET and INFO during rdb loading would have lied
      
      When loading rdb from the network, don't kill the server on short read (that can be a network error)
      
      Fix rdb check when performed on preamble AOF
      
      tests:
      run replication tests for diskless slave too
      make replication test a bit more aggressive
      Add test for diskless load swapdb
      2de544cf
  2. 15 Mar, 2018 1 commit
  3. 29 Dec, 2017 1 commit
    • Oran Agra's avatar
      fix processing of large bulks (above 2GB) · 60a4f12f
      Oran Agra authored
      - protocol parsing (processMultibulkBuffer) was limitted to 32big positions in the buffer
        readQueryFromClient potential overflow
      - rioWriteBulkCount used int, although rioWriteBulkString gave it size_t
      - several places in sds.c that used int for string length or index.
      - bugfix in RM_SaveAuxField (return was 1 or -1 and not length)
      - RM_SaveStringBuffer was limitted to 32bit length
      60a4f12f
  4. 25 Apr, 2016 1 commit
  5. 27 Jul, 2015 1 commit
  6. 26 Jul, 2015 2 commits
  7. 22 Oct, 2014 1 commit
  8. 17 Oct, 2014 3 commits
  9. 14 Oct, 2014 1 commit
    • antirez's avatar
      rio.c fdset target: tolerate (and report) a subset of FDs in error. · 2a436aae
      antirez authored
      Fdset target is used when we want to write an RDB file directly to
      slave's sockets. In this setup as long as there is a single slave that
      is still receiving our payload, we want to continue sennding instead of
      aborting. However rio calls should abort of no FD is ok.
      
      Also we want the errors reported so that we can signal the parent who is
      ok and who is broken, so there is a new set integers with the state of
      each fd. Zero is ok, non-zero is the errno of the failure, if avaialble,
      or a generic EIO.
      2a436aae
  10. 10 Oct, 2014 2 commits
  11. 22 Jan, 2014 1 commit
    • antirez's avatar
      Use fflush() before fsync() in rio.c. · 172f14d4
      antirez authored
      Incremental flushing in rio.c is only used to avoid huge kernel buffers
      synched to slow disks creating big latency spikes, so this fix has no
      durability implications, however it is certainly more correct to make
      sure that the FILE buffers are flushed to the kernel before calling
      fsync on the file descriptor.
      
      Thanks to Li Shao Kai for reporting this issue in the Redis mailing
      list.
      172f14d4
  12. 16 Jul, 2013 1 commit
  13. 24 Apr, 2013 1 commit
  14. 29 Nov, 2012 1 commit
    • antirez's avatar
      Introduced the Build ID in INFO and --version output. · 2f62c966
      antirez authored
      The idea is to be able to identify a build in a unique way, so for
      instance after a bug report we can recognize that the build is the one
      of a popular Linux distribution and perform the debugging in the same
      environment.
      2f62c966
  15. 08 Nov, 2012 1 commit
  16. 09 Apr, 2012 3 commits
  17. 23 Oct, 2011 1 commit
  18. 22 Sep, 2011 2 commits
  19. 13 May, 2011 1 commit