1. 19 Sep, 2016 1 commit
  2. 11 Aug, 2016 1 commit
  3. 09 Aug, 2016 2 commits
  4. 21 Jul, 2016 1 commit
    • antirez's avatar
      Avoid simultaneous RDB and AOF child process. · 0a628e51
      antirez authored
      This patch, written in collaboration with Oran Agra (@oranagra) is a companion
      to 780a8b1d. Together the two patches should avoid that the AOF and RDB saving
      processes can be spawned at the same time. Previously conditions that
      could lead to two saving processes at the same time were:
      
      1. When AOF is enabled via CONFIG SET and an RDB saving process is
         already active.
      
      2. When the SYNC command decides to start an RDB saving process ASAP in
         order to serve a new slave that cannot partially resynchronize (but
         only if we have a disk target for replication, for diskless
         replication there is not such a problem).
      
      Condition "1" is not very severe but "2" can happen often and is
      definitely good at degrading Redis performances in an unexpected way.
      
      The two commits have the effect of always spawning RDB savings for
      replication in replicationCron() instead of attempting to start an RDB
      save synchronously. Moreover when a BGSAVE or AOF rewrite must be
      performed, they are instead just postponed using flags that will try to
      perform such operations ASAP.
      
      Finally the BGSAVE command was modified in order to accept a SCHEDULE
      option so that if an AOF rewrite is in progress, when this option is
      given, the command no longer returns an error, but instead schedules an
      RDB rewrite operation for when it will be possible to start it.
      0a628e51
  5. 03 Jun, 2016 1 commit
  6. 25 Apr, 2016 1 commit
  7. 15 Feb, 2016 1 commit
  8. 17 Nov, 2015 1 commit
  9. 13 Nov, 2015 1 commit
  10. 01 Oct, 2015 2 commits
  11. 27 Jul, 2015 2 commits
  12. 26 Jul, 2015 6 commits
  13. 17 Jul, 2015 1 commit
  14. 21 Jan, 2015 1 commit
    • antirez's avatar
      AOF rewrite: set iterator var to NULL when freed. · 4433f5a7
      antirez authored
      The cleanup code expects that if 'di' is not NULL, it is a valid
      iterator that should be freed.
      
      The result of this bug was a crash of the AOF rewriting process if an
      error occurred after the DBs data are written and the iterator is no
      longer valid.
      4433f5a7
  15. 02 Jan, 2015 1 commit
  16. 29 Sep, 2014 3 commits
    • Matt Stancliff's avatar
      Clean up text throughout project · 12d0195b
      Matt Stancliff authored
        - Remove trailing newlines from redis.conf
        - Fix comment misspelling
        - Clarifies zipEncodeLength usage and a C API mention (#1243, #1242)
        - Fix cluster typos (inspired by @papanikge #1507)
        - Fix rewite -> rewrite in a few places (inspired by #682)
      
      Closes #1243, #1242, #1507
      12d0195b
    • zionwu's avatar
      Fix incorrect comments · a2583466
      zionwu authored
      error != success; and 0 != number of bytes written
      
      Closes #1806
      a2583466
    • Jan-Erik Rediger's avatar
      Fix many small typos · 0cb87481
      Jan-Erik Rediger authored
      Closes #1871
      0cb87481
  17. 16 Sep, 2014 2 commits
    • antirez's avatar
      Seek at the end of AOF after truncate call. · 878c089e
      antirez authored
      It is not clear if files open in append only mode will automatically fix
      their offset after a truncate(2) operation. This commit makes sure that
      we reposition the AOF file descriptor offset at the end of the file
      after a truncated AOF is loaded and trimmed to the last valid command.
      878c089e
    • antirez's avatar
      On AOF end of file, truncate the AOF to last valid command. · 0ba8fe1a
      antirez authored
      Recently we introduced the ability to load truncated AOFs, but
      unfortuantely the support was broken since the server, after loading the
      truncated AOF, continues appending to the file that is corrupted at the
      end. The problem is fixed only in the next AOF rewrite.
      
      This commit fixes the issue by truncating the AOF to the last valid
      opcode, and aborting if it is not possible to truncate the file
      correctly.
      0ba8fe1a
  18. 08 Sep, 2014 3 commits
  19. 13 Aug, 2014 1 commit
  20. 08 Jul, 2014 1 commit
  21. 05 Jul, 2014 2 commits
  22. 04 Jul, 2014 5 commits