FoundationDB's testing turns the rigorous up to 11 and I'm unaware of anybody else who's published a description of a testing approach that goes to quite the same extremes.
If that's just because I haven't noticed the others, I'd love to hear about them for comparison.
I found a dataloss bug in the first hour of testing FDB. I think their testing hype is a bit overhyped.
I also find it somewhat irritating that they won't take fixes or reports of problems with the storage engine because "we fixed this in redwood" when redwood is completely theoretical.
You've been able to use redwood since FDB 7.1 via ssd-redwood-1-experimental. Hardly theoretical.
Curious about that data loss bug. do you have a link? most bugs I've seen have to due with latency spikes and cluster unavailability. haven't seen any around data loss after transaction has committed.
Only after FoundationDB made it standard.
FoundationDB's testing turns the rigorous up to 11 and I'm unaware of anybody else who's published a description of a testing approach that goes to quite the same extremes.
If that's just because I haven't noticed the others, I'd love to hear about them for comparison.
I found a dataloss bug in the first hour of testing FDB. I think their testing hype is a bit overhyped.
I also find it somewhat irritating that they won't take fixes or reports of problems with the storage engine because "we fixed this in redwood" when redwood is completely theoretical.
You've been able to use redwood since FDB 7.1 via ssd-redwood-1-experimental. Hardly theoretical.
Curious about that data loss bug. do you have a link? most bugs I've seen have to due with latency spikes and cluster unavailability. haven't seen any around data loss after transaction has committed.