- 16 Sep, 2014 1 commit
- 
- 
antirez authoredThis 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 authoredThe 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 authoredAs discussed in issue #1945. 
- 
Salvatore Sanfilippo authoredLimit 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 authoredWhen 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 authoredBecause 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 authoredThe 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 authoredThere 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 authoredIncrease size of range request in getrange 
 
- 
- 02 Sep, 2014 2 commits
- 
- 
Matt Stancliff authoredPreviously, 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 authored32 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 authoredWe can save a little work by aborting when we enter the function if we're disconnected. 
- 
Paddy Byers authored
- 
Paddy Byers authored
 
- 
- 26 Aug, 2014 5 commits
- 
- 
antirez authoredAlso related to #1929. 
- 
antirez authoredThis closes issue #1929, the other part was fixed in the context of issue 
- 
antirez authoredThis 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 authored
- 
Salvatore Sanfilippo authoredMissing assert removal from sdsIncrLen() 
 
- 
- 25 Aug, 2014 9 commits
- 
- 
Mariano Pérez Rodríguez authoredCompanion for 8eeb1802, but dealing with hiredis. 
- 
antirez authored
- 
antirez authored
- 
antirez authored
- 
Matt Stancliff authored
- 
Matt Stancliff authoredWe 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 authoredThis 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 authoredCloses #1097 
- 
Matt Stancliff authoredClearly ip[32] is wrong, but it's less clear that buf[32] was wrong without further reading. 
 
-