4 ms·
ones that promote quickly-spawned, ephemeral processes and which rely on reboots for cleanup (Unix). The only modern OS I know of that "relies on reboots for c
by bitwize 12y ago
ones that promote quickly-spawned, ephemeral processes and which rely on reboots for cleanup (Unix).
The only modern OS I know of that "relies on reboots for cleanup" is, ironically enough, the one famously descended from VMS (I am of course talking about NT-kernel-family Windows).
And this is not a VAX vs. Unix story; it's a story about by-the-numbers IBMers who dress in the Right Clothes and say the Right Things being completely feckless in the face of a VAX, development and maintenance of which has quite a different tradition and culture, mainly consisting of scruffy guys who Get Shit Done. Of which there is not a lack in the Unix tradition either.
- derefr 12y ago> And this is not a VAX vs. Unix story A parable communicates a lesson, and the lesson "don't let ops people who have never run an architecture resembling yours near your machines" is kind of vacuous/trivial. Like I said, I'm looking for a piece of wisdom can be extracted from this story that's relevant for modern devops people. I think the lesson is basically: some systems evolved around doing discrete batch-processing tasks that throw away their arenas when they're done, and have very few and discrete connection points; while other systems are "about" living object graphs that can't be disentangled, only upgraded as an entire system, and which maintain themselves rather than having maintenance done upon them from outside. Rebooting solves problems with the former, since you're cleaning up all your temp files, cached intermediary results, etc. and then scheduling fresh new tasks. Rebooting the latter just makes it struggle to put itself back together exactly the way it was before. Think of power-cycling an LAMP "app-tier" server (Unixine) vs. a database server (Vaxine.)
- mwcampbell 12y agoI read the story. In what case would it be that disastrous to reboot a database server?
- lutusp 12y ago> In what case would it be that disastrous to reboot a database server? To assure data integrity, an interactive database system has to log off all its users and shut down open databases before rebooting. If the reboot can't be orchestrated that way, if users can't be logged off in an orderly way, there will be data loss.
- jmalicki 12y agoIf your database is ACID, you can pull the power on the server from the wall and have it instantly turn off w/o data loss. That's the entire point of transactions...
- lutusp 12y ago> If your database is ACID, you can pull the power on the server from the wall and have it instantly turn off w/o data loss. Yes -- all except the ongoing transactions at the users' workstations. That by itself could represent a serious synchronization problem. For a serious business, an emergency power system might represent a better choice.
- dllthomas 12y agoIf you've not pulled the plug on your users' workstations, the clients should be perfectly capable of retrying the broken transactions when the database comes back up. There can, of course, be constraints that make this impossible, but sloppy coding making it impossible is more common.
- newman314 12y agoIf your DB is ACID AND your underlying storage has not lied to you about committing the write...
- CaptainZapp 12y agoThis is the basic reason why raw devices where the way to go for decades for use as database devices and are still in use in most installations. I'm talking about Sybase here. But any database, which shifts the commit responsible to the operating system (without explicit guarantees that committed data is indeed written to disk) may invite you in for a huge and very unpleasant surprise.