History

Adding module api for processing commands during busy jobs and allow flagging the commands that should be handled at this status (#9963 )

Some modules might perform a long-running logic in different stages of Redis lifetime, for example:
* command execution
* RDB loading
* thread safe context

During this long-running logic Redis is not responsive.

This PR offers 
1. An API to process events while a busy command is running (`RM_Yield`)
2. A new flag (`ALLOW_BUSY`) to mark the commands that should be handled during busy
  jobs which can also be used by modules (`allow-busy`)
3. In slow commands and thread safe contexts, this flag will start rejecting commands with -BUSY only
  after `busy-reply-threshold`
4. During loading (`rdb_load` callback), it'll process events right away (not wait for `busy-reply-threshold`),
  but either way, the processing is throttled to the server hz rate.
5. Allow modules to Yield to redis background tasks, but not to client commands

* rename `script-time-limit` to `busy-reply-threshold` (an alias to the pre-7.0 `lua-time-limit`)

Co-authored-by: Oran Agra <oran@redislabs.com>

2022-01-20 09:05:53 +02:00

assets

Set repl-diskless-sync to yes by default, add repl-diskless-sync-max-replicas (#10092 )

2022-01-17 14:11:11 +02:00

cluster

Fix replica count check in migration tests. (#10140 )

2022-01-19 11:36:24 +02:00

helpers

When redis-cli received ASK, it didn't handle it (#8930 )

2021-08-02 14:59:08 +03:00

integration

Fix additional AOF filename issues. (#10110 )

2022-01-18 12:52:27 +02:00

modules

Adding module api for processing commands during busy jobs and allow flagging the commands that should be handled at this status (#9963 )

2022-01-20 09:05:53 +02:00

sentinel

Add sentinel config set test case (#10114 )

2022-01-19 11:57:51 +02:00

support

Set repl-diskless-sync to yes by default, add repl-diskless-sync-max-replicas (#10092 )

2022-01-17 14:11:11 +02:00

tmp

minor fixes to the new test suite, html doc updated

2010-05-14 18:48:33 +02:00

unit

Adding module api for processing commands during busy jobs and allow flagging the commands that should be handled at this status (#9963 )

2022-01-20 09:05:53 +02:00

instances.tcl

Set repl-diskless-sync to yes by default, add repl-diskless-sync-max-replicas (#10092 )

2022-01-17 14:11:11 +02:00

README.md

Add support for list type to store elements larger than 4GB (#9357 )

2021-11-03 20:47:18 +02:00

test_helper.tcl

Show the elapsed time of single test and speed up some tests (#10058 )

2022-01-05 13:49:01 +02:00

README.md

Redis Test Suite

The normal execution mode of the test suite involves starting and manipulating local redis-server instances, inspecting process state, log files, etc.

The test suite also supports execution against an external server, which is enabled using the --host and --port parameters. When executing against an external server, tests tagged external:skip are skipped.

There are additional runtime options that can further adjust the test suite to match different external server configurations:

Option	Impact
`--singledb`	Only use database 0, don't assume others are supported.
`--ignore-encoding`	Skip all checks for specific encoding.
`--ignore-digest`	Skip key value digest validations.
`--cluster-mode`	Run in strict Redis Cluster compatibility mode.
`--large-memory`	Enables tests that consume more than 100mb

Tags

Tags are applied to tests to classify them according to the subsystem they test, but also to indicate compatibility with different run modes and required capabilities.

Tags can be applied in different context levels:

start_server context
tags context that bundles several tests together
A single test context.

The following compatibility and capability tags are currently used:

Tag	Indicates
`external:skip`	Not compatible with external servers.
`cluster:skip`	Not compatible with `--cluster-mode`.
`large-memory`	Test that requires more than 100mb
`tls:skip`	Not campatible with `--tls`.
`needs:repl`	Uses replication and needs to be able to `SYNC` from server.
`needs:debug`	Uses the `DEBUG` command or other debugging focused commands (like `OBJECT`).
`needs:pfdebug`	Uses the `PFDEBUG` command.
`needs:config-maxmemory`	Uses `CONFIG SET` to manipulate memory limit, eviction policies, etc.
`needs:config-resetstat`	Uses `CONFIG RESETSTAT` to reset statistics.
`needs:reset`	Uses `RESET` to reset client connections.
`needs:save`	Uses `SAVE` to create an RDB file.

When using an external server (--host and --port), filtering using the external:skip tags is done automatically.

When using --cluster-mode, filtering using the cluster:skip tag is done automatically.

When not using --large-memory, filtering using the largemem:skip tag is done automatically.

In addition, it is possible to specify additional configuration. For example, to run tests on a server that does not permit SYNC use:

./runtest --host <host> --port <port> --tags -needs:repl