History

Harkrishn Patro fd3975684a

Propagate message to a node only if the cluster link is healthy. (#11752 )

Currently while a sharded pubsub message publish tries to propagate the message across the cluster, a NULL check is missing for clusterLink. clusterLink could be NULL if the link is causing memory beyond the set threshold cluster-link-sendbuf-limit and server terminates the link.

This change introduces two things:

Avoids the engine crashes on the publishing node if a message is tried to be sent to a node and the link is NULL.
Adds a debugging tool CLUSTERLINK KILL to terminate the clusterLink between two nodes.

2023-02-02 09:06:24 -08:00

assets

Fix --save command line regression in redis 7.0.0 (#10690 )

2022-05-09 13:37:49 +03:00

cluster

Harden init-tests for cluster tests (#11635 )

2022-12-22 17:37:00 -08:00

helpers

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

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

integration

Fix handshake timeout replication test race (#11773 )

2023-02-01 14:48:16 +02:00

modules

reprocess command when client is unblocked on keys (#11012 )

2023-01-01 23:35:42 +02:00

sentinel

Update Sentinel Debug command json file and add test case for it (#11513 )

2022-11-24 13:10:41 +02:00

support

Make assert_refcount skip the OBJECT REFCOUNT check with needs:debug tag (#11487 )

2022-11-22 16:38:27 +02:00

tmp

minor fixes to the new test suite, html doc updated

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

unit

Propagate message to a node only if the cluster link is healthy. (#11752 )

2023-02-02 09:06:24 -08:00

instances.tcl

Fix sentinel update loglevel tls test (#11528 )

2022-11-21 22:53:13 +02:00

README.md

Make assert_refcount skip the OBJECT REFCOUNT check with needs:debug tag (#11487 )

2022-11-22 16:38:27 +02:00

test_helper.tcl

Re-design cluster link send buffer to improve memory management (#11343 )

2022-11-01 19:26:44 -07: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 compatible 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 REFCOUNT`).
`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` or `BGSAVE` 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