3 ms·
Permanent and dramatic failure caused by SIGKILL presents a candidate for deletion, but it depends on your definitions of permanent and dramatic. It wouldn't b
by quesera 13y ago
Permanent and dramatic failure caused by SIGKILL presents a candidate for deletion, but it depends on your definitions of permanent and dramatic.
It wouldn't be unexpected for a SIGKILLed process to fail to flush a cache, or to exit with persistent state ...inconsistent. That can be permanent (changes lost) and dramatic.
You can wrap operations in transactional overhead to greatly reduce the chance of data loss, but you can't eliminate it entirely without assistance from peers.
kill -9 is the equivalent of unplugging the machine in the middle of operations. It might be fine, and with careful design it might be fine almost every time.
- zAy0LfpBZLC8mAC 13y agoWhy should "transactional overhead" not eliminate it entirely? And why "might be fine almost every time" instead of "will always be fine"?
- marcosdumay 13y agoInsert as many 9s you want in 99.9%, it'll still be a finite amount, so it's not "aways".
- zAy0LfpBZLC8mAC 13y agoThat doesn't change when you add peers, though, so it's kinda besides the point. Oh, and a normal shutdown doesn't prevent flipped bits due to cosmic rays either ...
- emmelaich 13y agoI think some mathematicians would disagree with you here :-)