- 25 Feb, 2014 6 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
An unit can abort in the middle for an error. The next unit should not assume that the instances are in a clean state, and must restart what was left killed.
-
antirez authored
Sentinel tests are designed to be dependent on the previous tests in the same unit, so usually we can't continue with the next test in the same unit if a previous test failed.
-
antirez authored
The test was previously performed by removing the master from the Sentinel monitored masters. The test with the Sentinels crashed is more similar to real-world partitions / failures.
-
antirez authored
Also kill_instance was modified to warn when a test will try to kill the same instance multiple times for error.
-
- 24 Feb, 2014 7 commits
-
-
antirez authored
The area a number of mandatory tests to craete a stable setup for testing that is not too sensitive to timing issues. All those tests moved to includes/init-tests, and marked as (init).
-
antirez authored
-
antirez authored
The new common initialization code used to start a new unit already set the timeout to 2000 milliseconds.
-
antirez authored
-
antirez authored
Now that we have a runtime configuration system, it is very important to be able to log how the Sentinel configuration changes over time because of API calls.
-
antirez authored
-
antirez authored
-
- 23 Feb, 2014 4 commits
-
-
antirez authored
-
antirez authored
Pause the test with running instances available for state inspection on error.
-
antirez authored
-
Salvatore Sanfilippo authored
Deny SYNC and PSYNC in redis-cli
-
- 22 Feb, 2014 2 commits
-
-
antirez authored
This error was conceived for the older version of Sentinel that worked via master redirection and that was not able to get configuration updates from other Sentinels via the Pub/Sub channel of masters or slaves. This reply does not make sense today, every Sentinel should reply with the best information it has currently. The error will make even more sense in the future since the plan is to allow Sentinels to update the configuration of other Sentinels via gossip with a direct chat without the prerequisite that they have at least a monitored instance in common.
-
antirez authored
It is now possible to kill and restart sentinel or redis instances for more real-world testing. The 01 unit tests the capability of Sentinel to update the configuration of Sentinels rejoining the cluster, however the test is pretty trivial and more tests should be added.
-
- 21 Feb, 2014 2 commits
-
-
Salvatore Sanfilippo authored
Add cluster or sentinel to proc title
-
Matt Stancliff authored
If you launch redis with `redis-server --sentinel` then in a ps, your output only says "redis-server IP:Port" — this patch changes the proc title to include [sentinel] or [cluster] depending on the current server mode: e.g. "redis-server IP:Port [sentinel]" "redis-server IP:Port [cluster]"
-
- 20 Feb, 2014 3 commits
- 19 Feb, 2014 3 commits
- 18 Feb, 2014 8 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
Rename define to match the new meaning.
-
antirez authored
If we can't reconfigure a slave in time during failover, go forward as anyway the slave will be fixed by Sentinels in the future, once they detect it is misconfigured. Otherwise a failover in progress may never terminate if for some reason the slave is uncapable to sync with the master while at the same time it is not disconnected.
-
- 17 Feb, 2014 5 commits
-
-
antirez authored
Nothing tested at all so far... Just the infrastructure spawning N Sentinels and N Redis instances that the test will use again and again.
-
antirez authored
-
antirez authored
Some inline test moved into server_is_up procedure. Also find_available_port was moved into util since it is going to be used for the Sentinel test as well.
-
antirez authored
The code tried to obtain the configuration file absolute path after processing the configuration file. However if config file was a relative path and a "dir" statement was processed reading the config, the absolute path obtained was wrong. With this fix the absolute path is obtained before processing the configuration while the server is still in the original directory where it was executed.
-
antirez authored
Now it logs the file name if it is not accessible. Also there is a different error for the missing config file case, and for the non writable file case.
-