Redis Persistent Rdb Snapshot persistence

Explanation 1: Although Redis is a single process, it has a separate sub-process for RDB operations, in order to ensure the consistency of the data, when the RDB operation fails, the main process stops writing

That's why stop-write-on-bgsave-error this order.

How do I stop an RDB?

Answer: The following three parameters will be masked out of the line

Getting Started with an RDB　　　　

First step: To modify the configuration file to allow 60 seconds to write 3,000 seconds to save the snapshot

　　　　　　

Step Two: Kill Redis restart Redis with the latest configuration files

　　　　　　

　　　　　　

Step three: Use Redis's own test tools for more than 3,000 writes

　　　　　　

Fourth step: Check the execution directory to generate a dump. RDB file

　　　　　　

Fifth step: If you kill Redis directly

Pkill-9 Redis

And then reboot,

The data previously triggered by the RDB is still there, but there is still some missing data that does not trigger the snapshot

The advantage is that because snapshot import is very fast,

The disadvantage is that there will be data loss

　　　　　　

　　　　　　　　　　

Redis Persistent Rdb Snapshot persistence