Ask HN: Ever worked with a service that can never be restarted?

Re:Ask HN: Ever worked with a service that can never be rest... by mrweasel on Thursday January 16, 2020 @10:16AM (#22065247)

> That system WILL FAIL.

I think that the key point. We have a system that can't easily be restarted and won't automatically start after a server is rebooted. The developers of the software don't care, because "what are the chances of a virtual machine spontaneously restarting". Turns out, those chances are rather good.

Servers, virtual machines, containers, doesn't matter, unless that thing is running on a mainframe, it will crash.

[ Parent | on HN ]

Re:Ask HN: Ever worked with a service that can never be rest... by andai on Thursday January 16, 2020 @12:00PM (#22066378)

What's special about mainframes in this context?

[ Parent | on HN ]

Re:Ask HN: Ever worked with a service that can never be rest... by DuskStar on Thursday January 16, 2020 @12:13PM (#22066537)

Mainframes tend to be designed with extreme uptime in mind - to the point of often having hot-swappable processors.

[ Parent | on HN ]

Re:Ask HN: Ever worked with a service that can never be rest... by marcosdumay on Thursday January 16, 2020 @01:48PM (#22067578)

The software doesn't care. It will crash anyway.

[ Parent | on HN ]

Re:Ask HN: Ever worked with a service that can never be rest... by DuskStar on Thursday January 16, 2020 @02:38PM (#22068046)

Oh, of course. But the MTBF for 'sleep 500y' on a mainframe is higher than on commodity x86 hardware.

[ Parent | on HN ]