2 ms·
I would love to hear more about "fsync saga" if you have any references. I know that PostgreSQL had "problems" with fsync(), but they never ended. They just a
by crabbone 4y ago
I would love to hear more about "fsync saga" if you have any references.
I know that PostgreSQL had "problems" with fsync(), but they never ended. They just accepted defeat, but so would everyone else who relies on filesystems to store their data. It's even more ingrained than that. The way hardware works, and, especially, the communication protocols around it (eg. SCSI or NVMe) are structured, fsync() is always going to be a problem.
- gizmo 4y agoSee this chain of articles: https://aphyr.com/posts/284-jepsen-mongodb https://aphyr.com/posts/284-jepsen-mongodb The mongodb organization repeatedly poo-pooed the issues with data loss, and only after repeated public exposure of the issues did they do anything about it. I don't know why people aggressively deny this when anybody can just google it and judge for themselves.
- threeseed 4y agoNo one denies anything or that the company handed it well. But this was never a real-world issue. All of the clients set safe defaults and the documentation was very clear about default fsync behaviour.
- crabbone 4y agoThanks! This was very interesting. But, did they actually fix this? The three posts are about the problems, but they go up to 3.X version of MongoDB, and the most recent seems to be at 6.X.