4 ms·
Killing the processes running on the compute element seems not very graceful, right? I'd expect a gracefully handled failure to have some state staved from whic
by bee_rider 5y ago
Killing the processes running on the compute element seems not very graceful, right? I'd expect a gracefully handled failure to have some state staved from which the computation can be continued.
Which would be overkill on a single node, given that CPUs don't really fail all that often.
- catern 5y agoIt's up to userspace to do more than that. There are other issues which can cause processes to be spontaneously killed (OOMkiller for example) so it's something you should be tolerant of.
- nickelpro 5y agoDisagree. An environment that's being reaped by OOMK is not stable enough to make assumptions about. You're in "go down the hall and turn it off and on again" territory. Attempting to account for such environments in user programs massively inflates their complexity, does little to enhance reliability, and the resulting behavior is typically brittle or outright broken from the get go. This is why, for example, the C++ committee flirts with making allocation failure a UB condition.
- astrange 5y agoiOS constantly runs an OOM killer and works pretty well.