summaryrefslogtreecommitdiff
path: root/tests/integration
Commit message (Collapse)AuthorAgeFilesLines
* prevent diskless replica from terminating on short readOran Agra2019-07-171-7/+90
| | | | | | | | now that replica can read rdb directly from the socket, it should avoid exiting on short read and instead try to re-sync. this commit tries to have minimal effects on non-diskless rdb reading. and includes a test that tries to trigger this scenario on various read cases.
* diskless replication on slave side (don't store rdb to file), plus some ↵Oran Agra2019-07-083-102/+161
| | | | | | | | | | | | | | | | | | | | | | | | | | | other related fixes The implementation of the diskless replication was currently diskless only on the master side. The slave side was still storing the received rdb file to the disk before loading it back in and parsing it. This commit adds two modes to load rdb directly from socket: 1) when-empty 2) using "swapdb" the third mode of using diskless slave by flushdb is risky and currently not included. other changes: -------------- distinguish between aof configuration and state so that we can re-enable aof only when sync eventually succeeds (and not when exiting from readSyncBulkPayload after a failed attempt) also a CONFIG GET and INFO during rdb loading would have lied When loading rdb from the network, don't kill the server on short read (that can be a network error) Fix rdb check when performed on preamble AOF tests: run replication tests for diskless slave too make replication test a bit more aggressive Add test for diskless load swapdb
* make replication tests more stable on slow machinesOran Agra2019-05-052-1/+30
| | | | | | | solving few replication related tests race conditions which fail on slow machines bugfix in slave buffers test: since the test is executed twice, each time with a different commands count, the threshold for the delta can't be a constant.
* Remove debugging printf from replication.tcl test.antirez2018-12-121-1/+0
|
* Slave removal: remove slave from integration tests descriptions.antirez2018-09-118-36/+36
|
* Test: processing of master stream in slave -BUSY state.antirez2018-08-311-0/+44
| | | | See #5297.
* Minor improvements to PR #5187.antirez2018-07-311-3/+7
|
* Fix typoJack Drogon2018-07-031-1/+1
|
* minor fix in creating a stream NACK for rdb and defrag testsOran Agra2018-06-271-1/+1
|
* add active defrag support for streamsOran Agra2018-06-271-0/+2
|
* Test RDB stream encoding saving/loading.antirez2018-06-191-0/+17
|
* Test: fix blocking lists/zsets replication test.antirez2018-05-151-3/+3
| | | | | By verifying that it was able to find a regression, and fixing it accordingly.
* Test: replication test blocking lists/zsets ops.antirez2018-05-151-0/+58
|
* AOF: run tests with preamble off when it makes sense.antirez2018-03-251-1/+1
|
* Fix integration test NOREPLICAS error time dependent false positive.antirez2018-01-241-3/+6
|
* Regression test for #4505 (Lua AUX field loading).antirez2017-12-041-1/+22
|
* Regression test: Slave restart with EVALSHA in backlog issue #4483.antirez2017-11-301-1/+64
|
* Regression test for #3899 fixed.antirez2017-04-281-19/+36
|
* Regression test for PSYNC2 issue #3899 added.antirez2017-04-281-0/+61
| | | | | | | | 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.
* Test: fix, hopefully, false PSYNC failure like in issue #2715.antirez2017-04-141-1/+1
| | | | | | | And many other related Github issues... all reporting the same problem. There was probably just not enough backlog in certain unlucky runs. I'll ask people that can reporduce if they see now this as fixed as well.
* Solaris fixes about tail usage and atomic vars.antirez2017-02-222-5/+5
| | | | | | | Testing with Solaris C compiler (SunOS 5.11 11.2 sun4v sparc sun4v) there were issues compiling due to atomicvar.h and running the tests also failed because of "tail" usage not conform with Solaris tail implementation. This commit fixes both the issues.
* Test: replication-psync, wait more to detect write load.antirez2017-02-221-1/+1
| | | | | | Slow systems like the original Raspberry PI need more time than 5 seconds to start the script and detect writes. After fixing the Raspberry PI can pass the unit without issues.
* Writable slaves expires: unit test.antirez2016-12-131-0/+12
|
* PSYNC2 test: check ability to resync after restart.antirez2016-11-291-1/+35
|
* PSYNC2 test: 20 seconds are enough...antirez2016-11-291-1/+5
|
* PSYNC2 test: modify the test for production.antirez2016-11-291-17/+33
|
* PSYNC2: stop sending newlines to sub-slaves when master is down.antirez2016-11-281-0/+1
| | | | | | | | | | | | | | | | | | | This actually includes two changes: 1) No newlines to take the master-slave link up when the upstream master is down. Doing this is dangerous because the sub-slave often is received replication protocol for an half-command, so can't receive newlines without desyncing the replication link, even with the code in order to cancel out the bytes that PSYNC2 was using. Moreover this is probably also not needed/sane, because anyway the slave can keep serving requests, and because if it's configured to don't serve stale data, it's a good idea, actually, to break the link. 2) When a +CONTINUE with a different ID is received, we now break connection with the sub-slaves: they need to be notified as well. This was part of the original specification but for some reason it was not implemented in the code, and was alter found as a PSYNC2 bug in the integration testing.
* PSYNC2: Test (WIP).antirez2016-11-281-0/+127
| | | | | | | This is the PSYNC2 test that helped find issues in the code, and that still can show a protocol desync from time to time. Work is in progress in order to find the issue. For now the test is not enabled in "make test" and must be run manually.
* Fix test for new RDB checksum failure message.antirez2016-07-041-1/+1
|
* Regression test for issue #2813.antirez2015-10-151-0/+53
|
* Fix RDB encoding test for new csvdump format.antirez2015-08-051-13/+13
|
* PSYNC test: also test the vanilla SYNC.antirez2015-08-051-18/+27
|
* Test PSYNC with diskless replication.antirez2015-08-041-13/+17
| | | | Thanks to Oran Agra from Redis Labs for providing this patch.
* Test: regression for issue #2473.antirez2015-03-271-8/+44
|
* Test: fix SPOP replication test count.antirez2015-03-131-1/+1
| | | | | If count is 0 SADD is called without element arguments, which is currently invalid.
* SPOP replication tests.antirez2015-02-111-0/+19
|
* alsoPropagate: handle REDIS_CALL_PROPAGATE and AOF loading.antirez2015-02-111-1/+1
|
* Added regression test for issue #2371.antirez2015-02-101-0/+24
|
* Fix RDB corruption test after server behavior change.antirez2015-02-041-1/+1
|
* Added <count> parameter to SPOP:Alon Diamant2014-12-141-0/+24
| | | | | | | | | spopCommand() now runs spopWithCountCommand() in case the <count> param is found. Added intsetRandomMembers() to Intset: Copies N random members from the set into inputted 'values' array. Uses either the Knuth or Floyd sample algos depending on ratio count/size. Added setTypeRandomElements() to SET type: Returns a number of random elements from a non empty set. This is a version of setTypeRandomElement() that is modified in order to return multiple entries, using dictGetRandomKeys() and intsetRandomMembers(). Added tests for SPOP with <count>: unit/type/set, unit/scripting, integration/aof -- Cleaned up code a bit to match with required Redis coding style
* Attempt to prevent false positives in replication test.antirez2014-11-241-11/+15
|
* Diskless replication tested with the multiple slaves consistency test.antirez2014-10-241-64/+67
|
* Remove trailing spaces from testsMatt Stancliff2014-09-291-5/+5
|
* Fix spelling in some test casesMatt Stancliff2014-09-291-1/+1
|
* Better truncated AOF loading tests.antirez2014-09-161-2/+29
| | | | | | Now there are tests to write more data after loading a truncated AOF, testing that the loaded data is correct, appending more, and testing again.
* Tests for aof-load-truncated = yes.antirez2014-09-081-1/+27
|
* AOF tests fixed turning aof-load-truncated to no.antirez2014-09-081-6/+6
| | | | | | | When aof-load-truncated option was introduced, with a default of "yes", the past behavior of the server to abort with trunncated AOF changed, so we need to explicitly configure the tests to abort with truncated AOF by setting the option to no.
* Test AOF format error detection.antirez2014-09-081-0/+25
|
* AOF loading: split handling of format errors from unexpected EOF.antirez2014-09-081-1/+1
|
* Test: AOF rewrite during write load.antirez2014-07-101-9/+0
|
View Lorry Controller Status