one thing to note about persistence, is that redis runs on memory so no matter how large the disk is, you are still restricted by the size of RAM on the node. the de facto for a primary store is an RDBMS for a very good reason, though redis persistence might be useful for some niches. Thanks for sharing the knowledge, great video!
Hi Raphael, everything is working fine like what you did in the video. However the redis.conf seems doesn't work. I tried to change save 10 1 in the redis.conf file and restart the container. Then when I check CONFIG GET save in redis-cli or redis insight it shows save "3600 1 300 100 60 1000". So redis.conf has no effect. Can you help please. TIA!!!
Hey! I just tried it out locally here once again and it's worked. - Are you sure you're mounting the correct file? - Also, when you try to start the container for the first time with the config file already edited, will it work? - One more thing to check, might be obvious 😅, but it's also worth mentioning that we must uncomment the save line (by removing the "#" in case you're editing the one you downloaded from GitHub: """ save 20 1 # save 300 100 this is commented """ These were my steps: 1. Moved the redis.conf file to /tmp/local-redis 2. Edited the file with "save 10 1" 2. Started the Docker Container by running: "docker run -d --name redis-stack -p 6379:6379 -p 8001:8001 -v /tmp/local-redis/data:/data -v /tmp/local-redis/redis.conf:/redis-stack.conf redis/redis-stack:latest" 3. Ran the CONFIG GET save command and saw: 1) "save" 2) "10 1" 4. Edited the file and changed "save 10 1" to "save 20 1" 5. Restarted the container 3. Ran the CONFIG GET save command and saw: 1) "save" 2) "20 1" Let me know if it works!
Just found you on Twitter! Really nice content! My 2 cents: Are you familiar to docker-compose? Docker commands can become quiet long and hard to remember. Using a docker-compose file you could manage things like ports, volumes, and other container configs (and do that for multiple containers at once) and run everything with simple commands.
This is the only source that helps me to understand redis persistence. Thanks!
Thank you so much for this feedback! I really appreciate it.
The way you present your course is simply excellent, Thank you ❣
Thank you for the feedback!
one thing to note about persistence, is that redis runs on memory so no matter how large the disk is, you are still restricted by the size of RAM on the node. the de facto for a primary store is an RDBMS for a very good reason, though redis persistence might be useful for some niches.
Thanks for sharing the knowledge, great video!
Thank you for pointing this out!
Awesome. Simple & In Depth.
Thank you for the feedback 🙏
This was exactly what I was looking for, thank you! 🤩
awesome
very straight forward
Thank you!
Great instruction, Thank you
Hi Raphael, everything is working fine like what you did in the video. However the redis.conf seems doesn't work. I tried to change save 10 1 in the redis.conf file and restart the container. Then when I check CONFIG GET save in redis-cli or redis insight it shows save "3600 1 300 100 60 1000". So redis.conf has no effect. Can you help please. TIA!!!
Hey! I just tried it out locally here once again and it's worked.
- Are you sure you're mounting the correct file?
- Also, when you try to start the container for the first time with the config file already edited, will it work?
- One more thing to check, might be obvious 😅, but it's also worth mentioning that we must uncomment the save line (by removing the "#" in case you're editing the one you downloaded from GitHub:
"""
save 20 1
# save 300 100 this is commented
"""
These were my steps:
1. Moved the redis.conf file to /tmp/local-redis
2. Edited the file with "save 10 1"
2. Started the Docker Container by running:
"docker run -d --name redis-stack -p 6379:6379 -p 8001:8001 -v /tmp/local-redis/data:/data -v /tmp/local-redis/redis.conf:/redis-stack.conf redis/redis-stack:latest"
3. Ran the CONFIG GET save command and saw:
1) "save"
2) "10 1"
4. Edited the file and changed "save 10 1" to "save 20 1"
5. Restarted the container
3. Ran the CONFIG GET save command and saw:
1) "save"
2) "20 1"
Let me know if it works!
Thank you! Do we need to enable this on the slave also?
Just found you on Twitter!
Really nice content!
My 2 cents: Are you familiar to docker-compose? Docker commands can become quiet long and hard to remember. Using a docker-compose file you could manage things like ports, volumes, and other container configs (and do that for multiple containers at once) and run everything with simple commands.
Yago, thank you for the comment! I appreciate it! I’m familiar with Docker Compose, great time-saving tool!
AOF sounds good
I am not able to get rdb file
awesome video , +1 subscribe
One Stop Solution for Redis Persistence
Thank you!
"nx - no expiry (ttl is not set)" - wrong. upd "only set the key if it does not already exist" - link for docs in answers
False