- 13 Jul, 2020 1 commit
-
-
Oran Agra authored
in the majority of the cases (on this rarely used feature) we want to stop and be able to connect to the shard with redis-cli. since these are two different processes interracting with the tty we need to stop both, and we'll have to hit enter twice, but it's not that bad considering it is rarely used.
-
- 10 Jul, 2020 2 commits
-
-
WuYunlong authored
-
Yossi Gottlieb authored
* Tests: fix and reintroduce redis-cli tests. These tests have been broken and disabled for 10 years now! * TLS: add remaining redis-cli support. This adds support for the redis-cli --pipe, --rdb and --replica options previously unsupported in --tls mode. * Fix writeConn().
-
- 23 Jun, 2020 1 commit
-
-
Oran Agra authored
In order to support the use of multi-exec in pipeline, it is important that MULTI and EXEC are never rejected and it is easy for the client to know if the connection is still in multi state. It was easy to make sure MULTI and DISCARD never fail (done by previous commits) since these only change the client state and don't do any actual change in the server, but EXEC is a different story. Since in the past, it was possible for clients to handle some EXEC errors and retry the EXEC, we now can't affort to return any error on EXEC other than EXECABORT, which now carries with it the real reason for the abort too. Other fixes in this commit: - Some checks that where performed at the time of queuing need to be re- validated when EXEC runs, for instance if the transaction contains writes commands, it needs to be aborted. there was one check that was already done in execCommand (-READONLY), but other checks where missing: -OOM, -MISCONF, -NOREPLICAS, -MASTERDOWN - When a command is rejected by processCommand it was rejected with addReply, which was not recognized as an error in case the bad command came from the master. this will enable to count or MONITOR these errors in the future. - make it easier for tests to create additional (non deferred) clients. - add tests for the fixes of this commit.
-
- 28 May, 2020 2 commits
- 27 May, 2020 1 commit
-
-
antirez authored
-
- 26 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
-
- 05 May, 2020 1 commit
-
-
antirez authored
-
- 17 Apr, 2020 1 commit
-
-
antirez authored
-
- 16 Apr, 2020 1 commit
-
-
Oran Agra authored
this test is time sensitive and it sometimes fail to pass below the latency threshold, even on strong machines. this test was the reson we're running just 2 parallel tests in the github actions CI, revering this.
-
- 06 Apr, 2020 1 commit
-
-
Oran Agra authored
-
- 25 Mar, 2020 1 commit
-
-
antirez authored
-
- 11 Mar, 2020 1 commit
-
-
bodong.ybd authored
-
- 21 Feb, 2020 2 commits
- 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.
-
- 10 May, 2019 1 commit
-
-
zhaozhao.zz authored
-
- 15 Apr, 2019 1 commit
-
-
antirez authored
-
- 24 Mar, 2019 1 commit
-
-
Yossi Gottlieb authored
-
- 18 Mar, 2019 1 commit
-
-
Yossi Gottlieb authored
-
- 28 Jan, 2019 1 commit
-
-
antirez authored
-
- 02 Aug, 2018 2 commits
- 31 Jul, 2018 1 commit
-
-
antirez authored
-
- 30 Jul, 2018 1 commit
-
-
Oran Agra authored
* allowing --single to be repeated * adding --only so that only a specific test inside a unit can be run * adding --skiptill useful to resume a test that crashed passed the problematic unit. useful together with --clients 1 * adding --skipfile to use a file containing list of tests names to skip * printing the names of the tests that are skiped by skipfile or denytags * adding --config to add config file options from command line
-
- 02 Jul, 2018 1 commit
-
-
WuYunlong authored
Issue #5063 added --wait-server option, but can not work.
-
- 01 Jul, 2018 1 commit
-
-
chendianqiang authored
-
- 26 Jun, 2018 1 commit
-
-
Oran Agra authored
* fail the test (exit code) in case of timeout. * add --wait-server to allow attaching a debugger * add --dont-clean to keep log files when tests are done
-
- 15 May, 2018 1 commit
-
-
antirez authored
-
- 15 Mar, 2018 1 commit
-
-
antirez authored
-
- 12 Mar, 2018 1 commit
-
-
Oran Agra authored
other fixes / improvements: - LUA script memory isn't taken from zmalloc (taken from libc malloc) so it can cause high fragmentation ratio to be displayed (which is false) - there was a problem with "fragmentation" info being calculated from RSS and used_memory sampled at different times (now sampling them together) other details: - adding a few more allocator info fields to INFO and MEMORY commands - improve defrag test to measure defrag latency of big keys - increasing the accuracy of the defrag test (by looking at real grag info) this way we can use an even lower threshold and still avoid false positives - keep the old (total) "fragmentation" field unchanged, but add new ones for spcific things - add these the MEMORY DOCTOR command - deduct LUA memory from the rss in case of non jemalloc allocator (one for which we don't "allocator active/used") - reduce sampling rate of the rss and allocator info
-
- 01 Dec, 2017 1 commit
-
-
antirez authored
-
- 28 Apr, 2017 1 commit
-
-
antirez authored
Experimentally verified that it can trigger the issue reverting the fix. At least on my system... Being the bug time/backlog dependant, it is very hard to tell if this test will be able to trigger the problem consistently, however even if it triggers the problem once in a while, we'll see it in the CI environment at http://ci.redis.io.
-
- 29 Nov, 2016 1 commit
-
-
antirez authored
-
- 18 Nov, 2016 1 commit
-
-
antirez authored
-
- 15 Jun, 2016 1 commit
-
-
antirez authored
-
- 31 May, 2016 1 commit
-
-
antirez authored
Thanks to @oranagra for noticing it was missing.
-
- 02 Mar, 2016 1 commit
-
-
antirez authored
-
- 09 Oct, 2015 1 commit
-
-
antirez authored
-