3 ms·
> Is there any reason to believe Yes, by the very nature of how redis implements persistence (RDF snapshot format + AOF) compared to traditional btree-backed s
by tomnipotent 5y ago
> Is there any reason to believe
Yes, by the very nature of how redis implements persistence (RDF snapshot format + AOF) compared to traditional btree-backed storage with WALs.
- samhw 5y agoCould you explain why that has a bearing on the risk of data loss? Note that AOF is a WAL. (Also, I think you mean RDB – unless you're talking about something else entirely of which I'm unaware?)
- tomnipotent 5y ago> Note that AOF is a WAL The redis AOF is written to after the command is executed and in-memory data is modified. It is not a WAL.
- samhw 5y agoAh, fair enough, that's true. It's written to the AOF before processing the next query (https://github.com/redis/redis/blob/unstable/src/server.c#L4396 https://github.com/redis/redis/blob/unstable/src/server.c#L4...), so I believe you get read-your-writes consistency per node (in terms of the AOF), but I suppose it is technically written afterwards rather than before.