mirror of
http://github.com/valkey-io/valkey
synced 2024-11-22 09:17:20 +00:00
20533cc1d7
In order to speed up tests, avoid saving an RDB (mostly notable on shutdown), except for tests that explicitly test the RDB mechanism In addition, use `shutdown-on-sigterm force` to prevetn shutdown from failing in case the server is in the middle of the initial AOFRW Also a a test that checks that the `shutdown-on-sigterm default` is to refuse shutdown if there's an initial AOFRW Co-authored-by: Guy Benoish <guy.benoish@redislabs.com>
38 lines
766 B
Plaintext
38 lines
766 B
Plaintext
# Redis configuration for testing.
|
|
|
|
always-show-logo yes
|
|
notify-keyspace-events KEA
|
|
daemonize no
|
|
pidfile /var/run/redis.pid
|
|
port 6379
|
|
timeout 0
|
|
bind 127.0.0.1
|
|
loglevel verbose
|
|
logfile ''
|
|
databases 16
|
|
latency-monitor-threshold 1
|
|
repl-diskless-sync-delay 0
|
|
|
|
# Turn off RDB by default (to speedup tests)
|
|
# Note the infrastructure in server.tcl uses a dict, we can't provide several save directives
|
|
save ''
|
|
|
|
rdbcompression yes
|
|
dbfilename dump.rdb
|
|
dir ./
|
|
|
|
slave-serve-stale-data yes
|
|
appendonly no
|
|
appendfsync everysec
|
|
no-appendfsync-on-rewrite no
|
|
activerehashing yes
|
|
|
|
enable-protected-configs yes
|
|
enable-debug-command yes
|
|
enable-module-command yes
|
|
|
|
propagation-error-behavior panic
|
|
|
|
# Make sure shutdown doesn't fail if there's an initial AOFRW
|
|
shutdown-on-sigterm force
|