- 22 Feb, 2021 1 commit
-
-
杨博东 authored
After fork, the child process(redis-aof-rewrite) will get the fd opened by the parent process(redis), when redis killed by kill -9, it will not graceful exit(call prepareForShutdown()), so redis-aof-rewrite thread may still alive, the fd(lock) will still be held by redis-aof-rewrite thread, and redis restart will fail to get lock, means fail to start. This issue was causing failures in the cluster tests in github actions. Co-authored-by:
Oran Agra <oran@redislabs.com> (cherry picked from commit cbaf3c5b)
-
- 27 Oct, 2020 1 commit
-
-
Oran Agra authored
I suppose that it was overlooked, since till recently none of the blocked commands were readonly. other changes: - add test for the above. - add better support for additional (and deferring) clients for cluster tests - improve a test which left the client in MULTI state. (cherry picked from commit 216c1106)
-
- 13 Aug, 2017 1 commit
-
-
Chris Lamb authored
-
- 15 Jan, 2016 2 commits
- 02 Jan, 2016 1 commit
-
-
antirez authored
-
- 29 Dec, 2015 1 commit
-
-
antirez authored
-
- 30 Mar, 2015 1 commit
-
-
antirez authored
-
- 22 Jan, 2015 1 commit
-
-
antirez authored
-
- 21 Jan, 2015 4 commits
-
-
antirez authored
Otherwise kill_instance + restart_instance in short succession will still find the port busy and will fail.
-
antirez authored
-
Matt Stancliff authored
-
Matt Stancliff authored
-
- 29 Sep, 2014 1 commit
-
-
Matt Stancliff authored
-
- 30 Jun, 2014 1 commit
-
-
antirez authored
-
- 18 Jun, 2014 1 commit
-
-
antirez authored
-
- 10 Jun, 2014 1 commit
-
-
antirez authored
-
- 19 May, 2014 1 commit
-
-
antirez authored
-
- 29 Apr, 2014 1 commit
-
-
antirez authored
-
- 24 Apr, 2014 2 commits
- 18 Mar, 2014 2 commits
- 04 Mar, 2014 4 commits
- 03 Mar, 2014 1 commit
-
-
antirez authored
-
- 25 Feb, 2014 2 commits
-
-
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
Also kill_instance was modified to warn when a test will try to kill the same instance multiple times for error.
-
- 23 Feb, 2014 2 commits
- 22 Feb, 2014 1 commit
-
-
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.
-
- 20 Feb, 2014 2 commits
- 18 Feb, 2014 3 commits
- 17 Feb, 2014 1 commit
-
-
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.
-