- 19 Sep, 2014 4 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
Salvatore Sanfilippo authored
Fix hiredis getaddrinfo leak
-
- 18 Sep, 2014 5 commits
-
-
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
-
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.
-
Salvatore Sanfilippo authored
Unix domain sockets incorrectly listed as IPv6.
-
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 4 commits
-
-
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.
-
- 15 Sep, 2014 2 commits
- 11 Sep, 2014 2 commits
-
-
antirez authored
-
antirez authored
The code to check the number of voters was never updated to follow the new Sentinel specification, so the number of voters was computed using only the set of Sentinels that provided a vote. This means that there is a changing majority on partitions, even if usually the issue is not triggered because of the configured quorum check (what was broken was the other implicit check that requires anyway half of the known sentinels to agree in order to start a failover).
-
- 10 Sep, 2014 2 commits
-
-
antirez authored
As discussed in issue #1945.
-
Salvatore Sanfilippo authored
Limit the *SCAN command `dictScan` iterations
-
- 09 Sep, 2014 1 commit
-
-
xiaost authored
*SCAN will cause redis server to hang for seconds after millions of keys was deleted by SCAN/DEL pairs
-
- 08 Sep, 2014 7 commits
-
-
antirez authored
-
antirez authored
When aof-load-truncated option was introduced, with a default of "yes", the past behavior of the server to abort with trunncated AOF changed, so we need to explicitly configure the tests to abort with truncated AOF by setting the option to no.
-
antirez authored
-
antirez authored
Because of the new ability to start with a truncated AOF, we need to correctly release all the memory on EOF error. Otherwise there is a small leak, that is not really a problem, but causes a false positive in the tests that detect memory leaks.
-
antirez authored
-
antirez authored
-
antirez authored
-
- 04 Sep, 2014 5 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
The original implementation was modified in order to allow to selectively announce a different IP or port, and to rewrite the two options in the config file after a rewrite.
-
Dara Kong authored
There are instances such as EC2 where the bind address is private (behind a NAT) and cannot be accessible from WAN. https://groups.google.com/d/msg/redis-db/PVVvjO4nMd0/P3oWC036v3cJ
-
- 03 Sep, 2014 1 commit
-
-
Salvatore Sanfilippo authored
Increase size of range request in getrange
-
- 02 Sep, 2014 2 commits
-
-
Matt Stancliff authored
Previously, GETRANGE of a key containing nothing ("") would allocate a large (size_t)-1 return value causing crashes on 32bit builds when it tried to allocate the 4 GB return string.
-
Matt Stancliff authored
32 bit builds don't have a big enough long to capture the same range as a 64 bit build. If we use "long long" we get proper size limits everywhere. Also updates size of unsigned comparison to fit new size of `end`. Fixes #1981
-
- 01 Sep, 2014 3 commits
-
-
Matt Stancliff authored
We can save a little work by aborting when we enter the function if we're disconnected.
-
Paddy Byers authored
-
Paddy Byers authored
-