В моем redis.conf, в разделе реплик, у меня есть:
################################# REPLICATION #################################
# replicaof <masterip> <masterport>
# masterauth <master-password>
replica-serve-stale-data yes
replica-read-only yes
repl-diskless-sync no
repl-diskless-sync-delay 5
repl-disable-tcp-nodelay no
# repl-backlog-size 1mb
# repl-backlog-ttl 3600
replica-priority 100
# replica-announce-ip 5.5.5.5
# replica-announce-port 1234
Итак ... У меня сложилось впечатление, что я не настраиваю своего рода REPLICA для своего сервера redis.
Однако, каждый раз, когда я перезагружаю свой сервер redis, я вижу эти журналы через 8 минут:
1:S 17 Jan 2020 21:29:12.618 * Before turning into a replica, using my master parameters to synthesize a cached master: I may be able to synchronize with the new master with just a partial transfer.
1:S 17 Jan 2020 21:29:12.618 * REPLICAOF XX.XXX.XX.XXX:8888 enabled (user request from 'id=2997 addr=YY.YYY.YYY.YYY:41454 fd=8 name= age=0 idle=0 flags=N db=0 sub=0 psub=0 multi=-1 qbuf=47 qbuf-free=32721 obl=0 oll=0 omem=0 events=r cmd=slaveof')
1:S 17 Jan 2020 21:29:12.621 * Connecting to MASTER XX.XXX.XX.XXX:8888
1:S 17 Jan 2020 21:29:12.622 * MASTER <-> REPLICA sync started
1:S 17 Jan 2020 21:29:12.662 * Non blocking connect for SYNC fired the event.
1:S 17 Jan 2020 21:29:12.702 * Master replied to PING, replication can continue...
1:S 17 Jan 2020 21:29:12.783 * Trying a partial resynchronization (request 6b69a379015e67268cc1c453b74594bfb7475b8e:1).
1:S 17 Jan 2020 21:29:12.823 * Full resync from master: ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ:1
1:S 17 Jan 2020 21:29:12.823 * Discarding previously cached master state.
1:S 17 Jan 2020 21:29:12.824 * MASTER <-> REPLICA sync: receiving 55640 bytes from master
1:S 17 Jan 2020 21:29:12.903 * MASTER <-> REPLICA sync: Flushing old data
1:S 17 Jan 2020 21:29:12.904 * MASTER <-> REPLICA sync: Loading DB in memory
1:S 17 Jan 2020 21:29:12.904 # Wrong signature trying to load DB from file
1:S 17 Jan 2020 21:29:12.904 # Failed trying to load the MASTER synchronization DB from disk
1:S 17 Jan 2020 21:29:13.628 * Connecting to MASTER XX.XXX.XX.XXX:8888
1:S 17 Jan 2020 21:29:13.629 * MASTER <-> REPLICA sync started
1:S 17 Jan 2020 21:29:13.665 * Non blocking connect for SYNC fired the event.
1:S 17 Jan 2020 21:29:13.700 # Error condition on socket for SYNC: Connection reset by peer
1:S 17 Jan 2020 21:29:14.634 * Connecting to MASTER XX.XXX.XX.XXX:8888
1:S 17 Jan 2020 21:29:14.635 * MASTER <-> REPLICA sync started
1:S 17 Jan 2020 21:29:14.670 * Non blocking connect for SYNC fired the event.
1:S 17 Jan 2020 21:29:14.721 # Error condition on socket for SYNC: Broken pipe
1:S 17 Jan 2020 21:29:15.649 * Connecting to MASTER XX.XXX.XX.XXX:8888
1:S 17 Jan 2020 21:29:15.649 * MASTER <-> REPLICA sync started
1:S 17 Jan 2020 21:29:15.691 * Non blocking connect for SYNC fired the event.
1:S 17 Jan 2020 21:29:15.733 # Error condition on socket for SYNC: Broken pipe
1:S 17 Jan 2020 21:29:16.654 * Connecting to MASTER XX.XXX.XX.XXX:8888
1:S 17 Jan 2020 21:29:16.655 * MASTER <-> REPLICA sync started
1:S 17 Jan 2020 21:29:16.691 * Non blocking connect for SYNC fired the event.
1:S 17 Jan 2020 21:29:16.726 # Error reply to PING from master: '-Reading from master: Resource temporarily unavailable'
1:S 17 Jan 2020 21:29:17.660 * Connecting to MASTER XX.XXX.XX.XXX:8888
1:S 17 Jan 2020 21:29:17.660 * MASTER <-> REPLICA sync started
1:S 17 Jan 2020 21:29:17.701 * Non blocking connect for SYNC fired the event.
1:S 17 Jan 2020 21:29:17.743 # Error condition on socket for SYNC: Connection reset by peer
1:S 17 Jan 2020 21:29:18.665 * Connecting to MASTER XX.XXX.XX.XXX:8888
1:S 17 Jan 2020 21:29:18.666 * MASTER <-> REPLICA sync started
1:S 17 Jan 2020 21:29:18.708 * Non blocking connect for SYNC fired the event.
1:S 17 Jan 2020 21:29:18.749 # Error condition on socket for SYNC: Broken pipe
1:S 17 Jan 2020 21:29:19.672 * Connecting to MASTER XX.XXX.XX.XXX:8888
1:S 17 Jan 2020 21:29:19.673 * MASTER <-> REPLICA sync started
1:S 17 Jan 2020 21:29:19.712 * Non blocking connect for SYNC fired the event.
1:S 17 Jan 2020 21:29:19.752 # Error reply to PING from master: '-Reading from master: Resource temporarily unavailable'
1:S 17 Jan 2020 21:29:19.827 * Module 'system' loaded from ./red2.so
1:M 17 Jan 2020 21:29:19.924 # Setting secondary replication ID to 6b69a379015e67268cc1c453b74594bfb7475b8e, valid up to offset: 1. New replication ID is 22584ed3770a10c7b93a4433ded8e8a0be22b02f
1:M 17 Jan 2020 21:29:19.924 * MASTER MODE enabled (user request from 'id=2997 addr=YY.YYY.YYY.YYY:41454 fd=8 name= age=7 idle=0 flags=N db=0 sub=0 psub=0 multi=-1 qbuf=34 qbuf-free=32734 obl=0 oll=0 omem=0 events=r cmd=slaveof')
1:M 17 Jan 2020 21:29:21.451 * Module system unloaded
Я не эксперт по безопасности, поэтому у меня все еще есть сомнения, был ли мой сервер redis скомпрометировано или если это просто неверная конфигурация redis: вот почему я сначала публикую здесь.
Так есть ли какой-нибудь процесс redis, который может иметь такое поведение MASTER-REPLICA по умолчанию, о котором я не знаю? Если да, то как его отключить?
PS: пока я установил пароль на redis, и, похоже, он решил проблему.