- 16 9月, 2014 4 次提交
-
-
由 antirez 提交于
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 提交于
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 提交于
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 提交于
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 9月, 2014 4 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
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 9月, 2014 6 次提交
-
-
由 antirez 提交于
As discussed in issue #1945.
-
由 xiaost 提交于
*SCAN will cause redis server to hang for seconds after millions of keys was deleted by SCAN/DEL pairs
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
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 提交于
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
-
- 08 9月, 2014 7 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
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 提交于
-
由 antirez 提交于
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 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
- 04 9月, 2014 2 次提交
-
-
由 Matt Stancliff 提交于
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 提交于
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 9月, 2014 4 次提交
-
-
由 antirez 提交于
-
由 Matt Stancliff 提交于
We can save a little work by aborting when we enter the function if we're disconnected.
-
由 Paddy Byers 提交于
-
由 Paddy Byers 提交于
-
- 27 8月, 2014 13 次提交
-
-
由 antirez 提交于
Also related to #1929.
-
由 antirez 提交于
This closes issue #1929, the other part was fixed in the context of issue
-
由 antirez 提交于
This allows to support datasets with more than 2 billion of keys (possible in very large memory instances, this bug was actually reported). Closes issue #1814.
-
由 antirez 提交于
-
由 Mariano Pérez Rodríguez 提交于
Companion for 8eeb1802, but dealing with hiredis.
-
由 antirez 提交于
-
由 Matt Stancliff 提交于
-
由 Matt Stancliff 提交于
We don't want scripts doing CLIENT SETNAME or CLIENT KILL or CLIENT LIST or CLIENT PAUSE. Originally reported by Chris Wj then proper action inspired by Itamar Haber. Reference: https://groups.google.com/forum/#!topic/redis-db/09B2EYwyVgk
-
由 Matt Stancliff 提交于
This just deletes old code that didn't get removed when logic changed. We were setting offsets that never got read anywhere. Since clients are now just cloned, we don't need to track per-client buffer offsets anywhere because they are all the same from the original client.
-
由 CharSyam 提交于
Closes #1097
-
由 Matt Stancliff 提交于
Clearly ip[32] is wrong, but it's less clear that buf[32] was wrong without further reading.
-
由 Eiichi Sato 提交于
Closes #1914
-
由 Jan-Erik Rediger 提交于
Once this is merged: - merge the latest changes to commands.json in antirez/redis-doc - re-run: utils/generate-command-help.rb > src/help.h Then we'll have nice and easy tab-completed help in redis-cli again. Closes #1909
-