首页
学习
活动
专区
工具
TVP
发布
社区首页 >问答首页 >我的Redis为什么每天数据都会丢失?

我的Redis为什么每天数据都会丢失?

提问于 2024-05-12 15:45:49
回答 0关注 1查看 22

我在云服务上使用redis单机,没有配置任何主从、集群之类的东西,但是每天我的数据库中的数据都会被清除掉,通过看日志文件,发现有主从复制失败等问题,我想知道为什么啊,如何解决数据每天不被清除掉。

代码语言:txt
复制
11626:M 11 May 2024 23:44:01.119 * Background saving terminated with success
11626:M 12 May 2024 00:44:02.049 * 1 changes in 3600 seconds. Saving...
11626:M 12 May 2024 00:44:02.049 * Background saving started by pid 23716
23716:C 12 May 2024 00:44:02.054 * DB saved on disk
23716:C 12 May 2024 00:44:02.054 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
11626:M 12 May 2024 00:44:02.150 * Background saving terminated with success
11626:M 12 May 2024 09:24:49.711 * 1 changes in 3600 seconds. Saving...
11626:M 12 May 2024 09:24:49.711 * Background saving started by pid 16880
16880:C 12 May 2024 09:24:49.716 * DB saved on disk
16880:C 12 May 2024 09:24:49.716 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
11626:M 12 May 2024 09:24:49.813 * Background saving terminated with success
11626:S 12 May 2024 09:24:49.931 * Before turning into a replica, using my own master parameters to synthesize a cached master: I may be able to synchronize with the new master with just a partial transfer.
11626:S 12 May 2024 09:24:49.932 * Connecting to MASTER 47.236.97.236:60108
11626:S 12 May 2024 09:24:49.932 * MASTER <-> REPLICA sync started
11626:S 12 May 2024 09:24:49.932 * REPLICAOF 47.236.97.236:60108 enabled (user request from 'id=3754 addr=101.201.119.233:47356 laddr=192.168.0.83:6379 fd=7 name= age=0 idle=0 flags=N db=0 sub=0 psub=0 ssub=0 multi=-1 qbuf=29 qbuf-free=20445 argv-mem=25 multi-mem=0 rbs=1024 rbp=668 obl=0 oll=0 omem=0 tot-mem=22449 events=r cmd=slaveof user=default redir=-1 resp=2 lib-name= lib-ver=')
11626:S 12 May 2024 09:24:50.131 * Non blocking connect for SYNC fired the event.
11626:S 12 May 2024 09:24:50.331 * Master replied to PING, replication can continue...
11626:S 12 May 2024 09:24:50.730 * Trying a partial resynchronization (request 8e68efb698e7166e33e8ac36a93ae8ecdfa0ecbb:1).
11626:S 12 May 2024 09:24:50.930 * Full resync from master: ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ:0
11626:S 12 May 2024 09:24:50.930 * MASTER <-> REPLICA sync: receiving 21816 bytes from master to disk
11626:S 12 May 2024 09:24:50.930 * MASTER <-> REPLICA sync: receiving 21816 bytes from master to disk
11626:S 12 May 2024 09:24:51.130 * Discarding previously cached master state.
11626:S 12 May 2024 09:24:51.130 * MASTER <-> REPLICA sync: Flushing old data
11626:S 12 May 2024 09:24:51.130 * MASTER <-> REPLICA sync: Loading DB in memory
11626:S 12 May 2024 09:24:51.134 # Wrong signature trying to load DB from file
11626:S 12 May 2024 09:24:51.134 # Failed trying to load the MASTER synchronization DB from disk, check server logs.
11626:S 12 May 2024 09:24:51.134 * Reconnecting to MASTER 47.236.97.236:60108 after failure
11626:S 12 May 2024 09:24:51.134 * MASTER <-> REPLICA sync started
11626:S 12 May 2024 09:24:51.323 * Non blocking connect for SYNC fired the event.
11626:S 12 May 2024 09:24:51.513 * Master replied to PING, replication can continue...
11626:S 12 May 2024 09:24:51.891 * Partial resynchronization not possible (no cached master)
11626:S 12 May 2024 09:24:52.081 * Full resync from master: ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ:0
11626:S 12 May 2024 09:24:52.081 * MASTER <-> REPLICA sync: receiving 21816 bytes from master to disk
11626:S 12 May 2024 09:24:52.270 * MASTER <-> REPLICA sync: Flushing old data
11626:S 12 May 2024 09:24:52.270 * MASTER <-> REPLICA sync: Loading DB in memory
11626:S 12 May 2024 09:24:52.274 # Wrong signature trying to load DB from file
11626:S 12 May 2024 09:24:52.274 # Failed trying to load the MASTER synchronization DB from disk, check server logs.
11626:S 12 May 2024 09:24:52.274 * Reconnecting to MASTER 47.236.97.236:60108 after failure
11626:S 12 May 2024 09:24:52.274 * MASTER <-> REPLICA sync started
11626:S 12 May 2024 09:24:52.477 * Non blocking connect for SYNC fired the event.
11626:S 12 May 2024 09:24:52.679 * Master replied to PING, replication can continue...
11626:S 12 May 2024 09:24:53.083 * Partial resynchronization not possible (no cached master)
11626:S 12 May 2024 09:24:53.286 * Full resync from master: ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ:0
11626:S 12 May 2024 09:24:53.286 * MASTER <-> REPLICA sync: receiving 21816 bytes from master to disk
11626:S 12 May 2024 09:24:53.488 * MASTER <-> REPLICA sync: Flushing old data
11626:S 12 May 2024 09:24:53.488 * MASTER <-> REPLICA sync: Loading DB in memory
11626:S 12 May 2024 09:24:53.492 # Wrong signature trying to load DB from file
11626:S 12 May 2024 09:24:53.492 # Failed trying to load the MASTER synchronization DB from disk, check server logs.
11626:S 12 May 2024 09:24:53.492 * Reconnecting to MASTER 47.236.97.236:60108 after failure
11626:S 12 May 2024 09:24:53.492 * MASTER <-> REPLICA sync started
11626:S 12 May 2024 09:24:53.680 * Non blocking connect for SYNC fired the event.
11626:S 12 May 2024 09:24:53.869 * Master replied to PING, replication can continue...
11626:S 12 May 2024 09:24:54.246 * Partial resynchronization not possible (no cached master)
11626:S 12 May 2024 09:24:54.435 * Full resync from master: ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ:0
11626:S 12 May 2024 09:24:54.435 * MASTER <-> REPLICA sync: receiving 21816 bytes from master to disk
11626:S 12 May 2024 09:24:54.623 * MASTER <-> REPLICA sync: Flushing old data
11626:S 12 May 2024 09:24:54.623 * MASTER <-> REPLICA sync: Loading DB in memory
11626:S 12 May 2024 09:24:54.627 # Wrong signature trying to load DB from file
11626:S 12 May 2024 09:24:54.627 # Failed trying to load the MASTER synchronization DB from disk, check server logs.
11626:S 12 May 2024 09:24:54.627 * Reconnecting to MASTER 47.236.97.236:60108 after failure
11626:S 12 May 2024 09:24:54.627 * MASTER <-> REPLICA sync started
11626:S 12 May 2024 09:24:54.826 * Non blocking connect for SYNC fired the event.
11626:M 12 May 2024 09:24:54.993 * Setting secondary replication ID to 8e68efb698e7166e33e8ac36a93ae8ecdfa0ecbb, valid up to offset: 1. New replication ID is 652b36f9faac47fb4261697e8004cfd4c3fe4b1c
11626:M 12 May 2024 09:24:54.993 * MASTER MODE enabled (user request from 'id=3754 addr=101.201.119.233:47356 laddr=192.168.0.83:6379 fd=7 name= age=5 idle=0 flags=N db=0 sub=0 psub=0 ssub=0 multi=-1 qbuf=16 qbuf-free=20458 argv-mem=12 multi-mem=0 rbs=1024 rbp=223 obl=0 oll=0 omem=0 tot-mem=22436 events=r cmd=slaveof user=default redir=-1 resp=2 lib-name= lib-ver=')
11626:M 12 May 2024 10:24:50.068 * 1 changes in 3600 seconds. Saving...
11626:M 12 May 2024 10:24:50.069 * Background saving started by pid 19824
19824:C 12 May 2024 10:24:50.073 * DB saved on disk
19824:C 12 May 2024 10:24:50.074 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
11626:M 12 May 2024 10:24:50.169 * Background saving terminated with success
11626:M 12 May 2024 13:04:32.698 # Possible SECURITY ATTACK detected. It looks like somebody is sending POST or Host: commands to Redis. This is likely due to an attacker attempting to use Cross Protocol Scripting to compromise your Redis instance. Connection from 124.70.90.23:27105 aborted.

回答

和开发者交流更多问题细节吧,去 写回答
相关文章

相似问题

相关问答用户
领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档