# does not immediately store an RDB on disk, it may cause data loss during

# failovers. RDB diskless load + Redis modules not handling I/O reads may also

# cause Redis to abort in case of I/O errors during the initial synchronization

# -----------------------------------------------------------------------------

#

# Replica can load the RDB it reads from the replication link directly from the

# socket, or store the RDB to a file and read that file after it was completely

#

# In many cases the disk is slower than the network, and storing and loading

# the RDB file may increase replication time (and even increase the master's

# AUTH (or the HELLO command AUTH option) in order to be authenticated and

# start to work.

#

#

# on Enable the user: it is possible to authenticate as this user.

# off Disable the user: it's no longer possible to authenticate

# It is possible to specify multiple patterns.

# allkeys Alias for ~*

# resetkeys Flush the list of allowed keys patterns.

# For example >mypass will add "mypass" to the list.

# This directive clears the "nopass" flag (see later).

# <<password> Remove this password from the list of valid passwords.

#

# Instead of configuring users here in this file, it is possible to use

# a stand-alone file just listing users. The two methods cannot be mixed:

# ACL file, the server will refuse to start.

#

# The format of the external ACL user file is exactly the same as the

# format that is used inside redis.conf to describe users.

#

# aclfile /etc/redis/users.acl

# layer on top of the new ACL system. The option effect will be just setting

# the password for the default user. Clients will still authenticate using

# AUTH <password> as usually, or more explicitly with AUTH default <password>

# it is possible to increase the expire "effort" that is normally set to

# "1", to a greater value, up to the value "10". At its maximum value the

# system will use more CPU, longer cycles (and technically may introduce

#

# active-expire-effort 1

#

# Now it is also possible to handle Redis clients socket reads and writes

# in different I/O threads. Since especially writing is so slow, normally

# core, and spawn multiple instances in order to scale more. Using I/O

# threads it is possible to easily speedup two times Redis without resorting

# to pipelining nor sharding of the instance.

#

# io-threads 4

#

# When I/O threads are enabled, we only use threads for writes, that is

# to thread the write(2) syscall and transfer the client buffers to the

# socket. However it is also possible to enable threading of reads and

#

# NOTE 2: If you want to test the Redis speedup using redis-benchmark, make

# sure you also run the benchmark itself in threaded mode, using the

# be able to notice the improvements.

############################## APPEND ONLY MODE ###############################

#

# When a long running script exceeds the maximum execution time only the

# SCRIPT KILL and SHUTDOWN NOSAVE commands are available. The first can be

# is the only way to shut down the server in the case a write command was

# already issued by the script but the user doesn't want to wait for the natural

# termination of the script.

# cluster-migration-barrier 1

# By default Redis Cluster nodes stop accepting queries if they detect there

# This way if the cluster is partially down (for example a range of hash slots

# are no longer covered) all the cluster becomes, eventually, unavailable.

# It automatically returns available as soon as all the slots are covered again.

# * cluster-announce-port

# * cluster-announce-bus-port

#

# bus port. The information is then published in the header of the bus packets

# so that other nodes will be able to correctly map the address of the node

# publishing the information.

# Note that when remapped, the bus port may not be at the fixed offset of

# clients port + 10000, so you can specify any port and bus-port depending

# on how they get remapped. If the bus-port is not set, a fixed offset of

#

# Example:

#

# two kind of inline requests that were anyway illegal: an empty request

# or any request that starts with "/" (there are no Redis commands starting

# with such a slash). Normal RESP2/RESP3 requests are completely out of the

#

# If you open a connection to Redis when Gopher is enabled and send it

# a string like "/foo", if there is a key named "/foo" it is served via the

#

# Since the default HZ value by default is conservatively set to 10, Redis

# offers, and enables by default, the ability to use an adaptive HZ value

#

# When dynamic HZ is enabled, the actual configured HZ will be used as

# as a baseline, but multiples of the configured HZ value will be actually

# for the key counter to be divided by two (or decremented if it has a value

# less <= 10).

#

# decay the counter every time it happens to be scanned.

#

# lfu-log-factor 10

# restart is needed in order to lower the fragmentation, or at least to flush

# away all the data and create it again. However thanks to this feature

# implemented by Oran Agra for Redis 4.0 this process can happen at runtime

#

# Basically when the fragmentation is over a certain level (see the

# configuration options below) Redis will start to create new copies of the