- 01 Sep, 2020 2 commits
-
-
Oran Agra authored
When runtest-cluster, at first, we need to create a cluster use spawn_instance, a port which is not used is choosen, however sometimes we can't run server on the port. possibley due to a race with another process taking it first. such as redis/redis/runs/896537490. It may be due to the machine problem or In order to reduce the probability of failure when start redis in runtest-cluster, we attemp to use another port when find server do not start up. Co-authored-by:
Oran Agra <oran@redislabs.com> Co-authored-by:
yanhui13 <yanhui13@meituan.com> (cherry picked from commit e2d64485)
-
杨博东 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)
-
- 20 Jul, 2020 1 commit
-
- 28 May, 2020 1 commit
-
-
Oran Agra authored
apparently when running tests in parallel (the default of --clients 16), there's a chance for two tests to use the same port. specifically, one test might shutdown a master and still have the replica up, and then another test will re-use the port number of master for another master, and then that replica will connect to the master of the other test. this can cause a master to count too many full syncs and fail a test if we run the tests with --single integration/psync2 --loop --stop see Probmem 2 in #7314
-
- 07 Oct, 2019 1 commit
-
-
Yossi Gottlieb authored
* Introduce a connection abstraction layer for all socket operations and integrate it across the code base. * Provide an optional TLS connections implementation based on OpenSSL. * Pull a newer version of hiredis with TLS support. * Tests, redis-cli updates for TLS support.
-
- 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 2 commits