Answer the question
In order to leave comments, you need to log in
What to do with Redis after a reboot?
Please explain, I don't understand the point. Here is Redis, stores information in memory. OK. You counted something, learned something there and threw it into it. The client poke there and takes the data on keys. It seems logical and understandable. But here there was a server reboot, and what? After all, the data is lost and you have to write it down again, or is there a cast somewhere? I don't understand the applicability. Always used DBMS. He did something, counted something - saved it, and when necessary - pulled it out.
Answer the question
In order to leave comments, you need to log in
You can configure saving the database to permanent memory. There are options:
1. Saving the database with each write operation. It should be used only if it is critical for you to save all the data.
2. creating snapshots at time intervals. This is enabled by default. It is more optimal if the loss of data from the last snapshot to the server reboot is not so critical.
Here is the redis.io/topics/persistence documentation
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question