News for hackers. Stuff that matters.
Re:Redis on Acid: 0.5M ops/sec, 1ms latency and ACID compliance by antirez on Tuesday July 25, 2017 @10:08AM (#14847783)
Hello, I'm not sure of the setup Redis Labs is using, but vanilla Redis AOF does not allow partially-applied updates. Not for Redis transactions (MULTI/EXEC) nor with scripting. The same happens in the replication channel. In order to enforce this, Redis goes a very long way to avoid partial applications of Lua scripts, more info are in the EVAL page and in the -BUSY error in case of scripts not returning that already made writes.
Re:Redis on Acid: 0.5M ops/sec, 1ms latency and ACID compliance by aaronblohowiak on Tuesday July 25, 2017 @10:32AM (#14847980)
ah, thank you. I should have checked the docs! It is nice to know that you are writing the script and multi/exec semantics into the AOF log (at least in the default config) and that my guess is wrong.

I still wonder what the details are around the "almost" in "almost always" and stand by the conclusion that "almost atomic" is not the same as "atomic".

Re:Redis on Acid: 0.5M ops/sec, 1ms latency and ACID compliance by antirez on Tuesday July 25, 2017 @10:48AM (#14848103)
My best guess is that the author is referring to the fact that there are no rollbacks in Redis transactions, but I'm not sure. I'll try to ask internally. Thanks!