Changing Fedora's shutdown timeouts
Changing Fedora's shutdown timeouts
Posted Jan 24, 2023 9:49 UTC (Tue) by Wol (subscriber, #4433)In reply to: Changing Fedora's shutdown timeouts by kleptog
Parent article: Changing Fedora's shutdown timeouts
"The decision to commit or abort". LOOK AT IT FROM THE USER'S POINT OF VIEW. That decision is a no-brainer. ABORT IS UNACCEPTABLE.
Everybody's looking at it from the database's POV - "protect the database". Nobody's looking at it from the user's POV - "protect the data".
The correct sequence of events is the user confirms checkout, the database accepts the transaction, flushes it to the log, and doesn't return "purchase confirmed" until that log is safely on disk.
But if you've got a bunch of containers/vms/whatever on a machine in the cloud/your own cloud, can you guarantee that that log is safe? With all those layers of indirection in the way? Especially if the *container* confirms receipt of the log to the database, without the container itself checking that the layer below - and the layer below that etc etc - has really truly flushed the transaction? It's Russian Roulette.
Yup. If the software is well written, everything is fine. But can you guarantee that the stack is behaving as you expect / as it should?
Cheers,
Wol
The LWN site is currently under high scraper load, so comment display has been suppressed for anonymous users. If you are a human, you may read the comments by clicking the button below:
Note: you can avoid this step in the future by logging into your LWN account.
