Выключена репликация keydb

compose.yml

@@ -23,10 +23,9 @@ services:
     user: ${KEYDB_UID}:${KEYDB_GID}
     entrypoint: ["sh", "/entrypoint.sh"]
     volumes:
-      - ./docker/keydb/keydb.conf:/etc/keydb/keydb.conf
       - ./docker/keydb/entrypoint.sh:/entrypoint.sh
+      - ./docker/keydb/keydb.conf:/etc/keydb/keydb.conf
       - ./docker/keydb/data/:/data:rw
-      - ./log/keydb:/var/log/keydb/:rw
     ports:
       - ${KEYDB_PORT:-6379}:6379
 

docker/keydb/keydb.conf

@@ -526,7 +526,7 @@ replicaof no one
 #    UNSUBSCRIBE, PSUBSCRIBE, PUNSUBSCRIBE, PUBLISH, PUBSUB, COMMAND, POST,
 #    HOST and LATENCY.
 #
-replica-serve-stale-data no
+replica-serve-stale-data yes
 
 # Active Replicas will allow read only data access while loading remote RDBs
 # provided they are permitted to serve stale data.  As an option you may also
@@ -556,7 +556,7 @@ replica-serve-stale-data no
 # such as CONFIG, DEBUG, and so forth. To a limited extent you can improve
 # security of read only replicas using 'rename-command' to shadow all the
 # administrative / dangerous commands.
-replica-read-only yes
+replica-read-only no
 
 # Replication SYNC strategy: disk or socket.
 #
@@ -2060,7 +2060,7 @@ server-threads 2
 # Uncomment the option below to enable Active Active support.  Note that
 # replicas will still sync in the normal way and incorrect ordering when
 # bringing up replicas can result in data loss (the first master will win).
-# active-replica yes
+active-replica no
 
 # KeyDB will attempt to balance clients across threads evenly; However, replica clients
 # are usually much more expensive than a normal client, and so KeyDB will try to assign