- 24 Aug, 2016 1 commit
-
-
antirez authored
-
- 27 Jul, 2016 1 commit
-
-
antirez authored
By grepping the continuous integration errors log a number of GEORADIUS tests failures were detected. Fortunately when a GEORADIUS failure happens, the test suite logs enough information in order to reproduce the problem: the PRNG seed, coordinates and radius of the query. By reproducing the issues, three different bugs were discovered and fixed in this commit. This commit also improves the already good reporting of the fuzzer and adds the failure vectors as regression tests. The issues found: 1. We need larger squares around the poles in order to cover the area requested by the user. There were already checks in order to use a smaller step (larger squares) but the limit set (+/- 67 degrees) is not enough in certain edge cases, so 66 is used now. 2. Even near the equator, when the search area center is very near the edge of the square, the north, south, west or ovest square may not be able to fully cover the specified radius. Now a test is performed at the edge of the initial guessed search area, and larger squares are used in case the test fails. 3. Because of rounding errors between Redis and Tcl, sometimes the test signaled false positives. This is now addressed. Whenever possible the original code was improved a bit in other ways. A debugging example stanza was added in order to make the next debugging session simpler when the next bug is found.
-
- 22 Jul, 2016 2 commits
-
-
antirez authored
-
antirez authored
During the initial handshake with the master a slave will report to have a very high disconnection time from its master (since technically it was disconnected since forever, so the current UNIX time in seconds is reported). However when the slave is connected again the Sentinel may re-scan the INFO output again only after 10 seconds, which is a long time. During this time Sentinels will consider this instance unable to failover, so a useless delay is introduced. Actaully this hardly happened in the practice because when a slave's master is down, the INFO period for slaves changes to 1 second. However when a manual failover is attempted immediately after adding slaves (like in the case of the Sentinel unit test), this problem may happen. This commit changes the INFO period to 1 second even in the case the slave's master is not down, but the slave reported to be disconnected from the master (by publishing, last time we checked, a master disconnection time field in INFO). This change is required as a result of an unrelated change in the replication code that adds a small delay in the master-slave first synchronization.
-
- 06 Jul, 2016 1 commit
-
-
antirez authored
-
- 04 Jul, 2016 1 commit
-
-
antirez authored
-
- 28 Jun, 2016 3 commits
- 15 Jun, 2016 2 commits
- 05 Jun, 2016 1 commit
-
-
Pierre Chapuis authored
-
- 31 May, 2016 2 commits
- 18 May, 2016 1 commit
-
-
antirez authored
-
- 06 May, 2016 1 commit
-
-
antirez authored
-
- 05 May, 2016 2 commits
- 02 May, 2016 1 commit
-
-
antirez authored
The test works but is very slow so far, since it involves resharding 1/5 of all the cluster slots from master 0 to the other 4 masters and back into the original master.
-
- 25 Apr, 2016 1 commit
-
-
Oran Agra authored
-
- 18 Apr, 2016 1 commit
-
-
Damian Janowski authored
-
- 02 Mar, 2016 4 commits
- 18 Feb, 2016 1 commit
-
-
antirez authored
-
- 17 Feb, 2016 1 commit
-
-
antirez authored
Now elements added to lists are incremental numbers in order to understand, when inconsistencies are found, what is the order in which the elements were added. Also the error now provides both the expected and found value.
-
- 02 Feb, 2016 1 commit
-
-
antirez authored
-
- 15 Jan, 2016 2 commits
- 08 Jan, 2016 1 commit
-
-
antirez authored
This fix, provided by Paul Kulchenko (@pkulchenko), allows the Lua scripting engine to evaluate statements with a trailing comment like the following one: EVAL "print() --comment" 0 Lua can't parse the above if the string does not end with a newline, so now a final newline is always added automatically. This does not change the SHA1 of scripts since the SHA1 is computed on the body we pass to EVAL, without the other code we add to register the function. Close #2951.
-
- 02 Jan, 2016 1 commit
-
-
antirez authored
-
- 29 Dec, 2015 1 commit
-
-
antirez authored
-
- 18 Dec, 2015 1 commit
-
-
antirez authored
-
- 17 Dec, 2015 1 commit
-
-
antirez authored
It's a key invariant that when AOF is enabled, after the cluster reshards, a crash-recovery event causes all the keys to be still fine with the expected logical content. Now this is part of unit 04.
-
- 11 Dec, 2015 2 commits
- 10 Dec, 2015 2 commits
-
-
antirez authored
The old version was modeled with two failovers, however after the first it is possible that another slave will migrate to the new master, since for some time the new master is not backed by any slave. Probably there should be some pause after a failover, before the migration. Anyway the test is simpler in this way, and depends less on timing.
-
antirez authored
-
- 28 Nov, 2015 1 commit
-
-
antirez authored
64 bit double math is not enough to make the test passing, and rounding to 1.2999999 instead of 1.23 is not an error in the implementation. Valgrind and sometimes other archs are not able to work with 80 bit doubles.
-