- 29 Oct, 2014 3 commits
-
-
antirez authored
We need to remember what is the saving strategy of the current RDB child process, since the configuration may be modified at runtime via CONFIG SET and still we'll need to understand, when the child exists, what to do and for what goal the process was initiated: to create an RDB file on disk or to write stuff directly to slave's sockets.
-
antirez authored
-
antirez authored
During the replication full resynchronization process, the RDB file is transfered from the master to the slave. However there is a short preamble to send, that is currently just the bulk payload length of the file in the usual Redis form $..length..<CR><LF>. This preamble used to be sent with a direct write call, assuming that there was alway room in the socket output buffer to hold the few bytes needed, however this does not scale in case we'll need to send more stuff, and is not very robust code in general. This commit introduces a more general mechanism to send a preamble up to 2GB in size (the max length of an sds string) in a non blocking way.
-
- 06 Oct, 2014 28 commits
-
-
antirez authored
-
Miguel Parramon authored
😄 Closes #2034 -
Ezequiel Lovelle authored
Closes #2029
-
Gregory Petrosyan authored
Closes #2002
-
Matt Stancliff authored
-
Juarez Bochi authored
Closes #1960
-
T.J. Schuck authored
Closes #1938
-
Matt Stancliff authored
Some language in the comment was difficult to understand, so this commit: clarifies wording, removes unnecessary words, and relocates some dependent clauses closer to what they actually describe. I also tried to break up longer chains of thought (if X, then Y, and Q, and also F, so obviously M) into more manageable chunks for ease of understanding.
-
Matt Stancliff authored
-
Matt Stancliff authored
-
Jan-Erik Rediger authored
Closes #1739
-
Xiaojie Zhang authored
Closes #1523
-
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
-
Matt Stancliff authored
-
Aaron Rutkovsky authored
Closes #1513
-
Ben authored
Closes #1441
-
xuxiang authored
Closes #1386
-
Ted Nyman authored
Closes #1373
-
Michael Parker authored
Closes #1351
-
Jan-Erik Rediger authored
Closes #1871
-
zionwu authored
error != success; and 0 != number of bytes written Closes #1806
-
Jan-Erik Rediger authored
Closes #1713
-
Juarez Bochi authored
Closes #1682
-
Agis Anastasopoulos authored
Closes #1544
-
Jan-Erik Rediger authored
Closes #1537
-
Matt Stancliff authored
The core linenoise code was being backported, but not the README or example. It's less confusing for users if everything matches across directories. Fix inspired by @thrig Closes #1872
-
Manuel Meurer authored
Closes #1897
-
Lynn authored
Closes #1877
-
- 22 Sep, 2014 1 commit
-
-
antirez authored
-
- 19 Sep, 2014 2 commits
-
-
antirez authored
-
Matt Stancliff authored
Fixed in Redis by 1a5e5b6b, but since that part of code is largely copy/paste from Redis, the fix needs to be ported over too. Closes #2012
-
- 16 Sep, 2014 5 commits
-
-
antirez authored
-
antirez authored
Now there are tests to write more data after loading a truncated AOF, testing that the loaded data is correct, appending more, and testing again.
-
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.
-
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.
-
antirez authored
This is a general fix (check that dirty delta is positive) but actually should have as the only effect fixing the SAVE propagation to AOF and slaves.
-
- 12 Sep, 2014 1 commit
-
-
antirez authored
-