- 15 Oct, 2014 2 commits
- 14 Oct, 2014 3 commits
-
-
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.
-
antirez authored
-
antirez authored
-
- 10 Oct, 2014 3 commits
- 08 Oct, 2014 1 commit
-
-
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.
-
- 07 Oct, 2014 2 commits
- 03 Oct, 2014 1 commit
-
-
antirez authored
However we don't try to do this if the integer is already inside a range representable with a shared integer. The performance gain appears to be around ~15% in micro benchmarks, however in the long run this also helps to improve locality, so should have more, hard to measure, benefits.
-
- 29 Sep, 2014 17 commits
-
-
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.
-
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
-
Michael Parker authored
Closes #1351
-
Ted Nyman authored
Closes #1373
-
xuxiang authored
Closes #1386
-
Aaron Rutkovsky authored
Closes #1513
-
Jan-Erik Rediger authored
Closes #1537
-
Juarez Bochi authored
Closes #1682
-
zionwu authored
error != success; and 0 != number of bytes written Closes #1806
-
Jan-Erik Rediger authored
Closes #1871
-
Lynn authored
Closes #1877
-
- 26 Sep, 2014 1 commit
-
-
antirez authored
-
- 25 Sep, 2014 1 commit
-
-
antirez authored
The old DEBUG POPULATE form for automatic creation of test keys is: DEBUG POPULATE <count> Now an additional form is available: DEBUG POPULATE <count> <prefix> When prefix is not specified, it defaults to "key", so the keys are named incrementally from key:0 to key:<count-1>. Otherwise the specified prefix is used instead of "key". The command is useful in order to populate different Redis instances with key names guaranteed to don't collide. There are other debugging uses, for example it is possible to add additional N keys using a count of N and a random prefix at every call.
-
- 18 Sep, 2014 3 commits
-
-
antirez authored
Following the CLIENT LIST output format, we prefix the unix socket address with a "/" so that it is different than an IPv4/6 address. This makes parsing simpler. Related to #2010.
-
antirez authored
Related to PR #2010.
-
Yossi Gottlieb authored
-
- 17 Sep, 2014 2 commits
-
-
antirez authored
This fixes a potential bug that was never observed in practice since what happens is that the asynchronous connect returns ok (to fail later, calling the handler) every time, so a ping is queued, and sent_ping happens to always be populated. Howver technically connect(2) with a non blocking socket may return an error synchronously, so before this fix the code was not correct.
-
antirez authored
-
- 16 Sep, 2014 3 commits
-
-
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.
-
- 11 Sep, 2014 1 commit
-
-
antirez authored
-