You can configure different save points where an RDB is produced (for instance after at least five minutes and 100 writes against the data set, you can have multiple save points). RDB is NOT good if you need to minimize the chance of data loss in case Redis stops working (for example after a power outage).On replicas, RDB supports partial resynchronizations after restarts and failovers.RDB allows faster restarts with big datasets compared to AOF.The parent process will never perform disk I/O or alike. RDB maximizes Redis performances since the only work the Redis parent process needs to do in order to persist is forking a child that will do all the rest.RDB is very good for disaster recovery, being a single compact file that can be transferred to far data centers, or onto Amazon S3 (possibly encrypted).This allows you to easily restore different versions of the data set in case of disasters. For instance you may want to archive your RDB files every hour for the latest 24 hours, and to save an RDB snapshot every day for 30 days. RDB is a very compact single-file point-in-time representation of your Redis data.To learn more about how to evaluate your Redis persistence strategy, read on. If you'd rather not think about the tradeoffs between these different persistence strategies, you may want to consider Redis Enterprise's persistence options, which can be pre-configured using a UI.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |