4 ms·

So Stripe is the company that configured their master to no persistence, killed it, and blamed Redis for losing their data? Annoying they reported the "issue" t

by meritt 12y ago

So Stripe is the company that configured their master to no persistence, killed it, and blamed Redis for losing their data? Annoying they reported the "issue" to Aphyr, decided to withhold their name, and proceeded to spread a ton of FUD against Redis when the core issue was a mis-configuration on their part. Hand-holding can only go so far.

gdb 12y ago
The main point of the post is that if there's a configuration you expect to work, you need to test it, independent of whether or not it's supported by the author. I can think of a dozen other distributed system failures I've seen that happened despite using stock configuration — this particular failure was simply a recent example, and helps illustrate why game days are so valuable. On the plus side, Antirez has said that this configuration will soon be supported: https://news.ycombinator.com/item?id=8522630 https://news.ycombinator.com/item?id=8522630 (thanks Antirez!), so future users will be able to run in this configuration safely.