Bastion – Highly-available distributed fault-tolerant runtime

Re:Bastion – Highly-available distributed fault-tolerant run... by elteto on Monday February 24, 2020 @12:54PM (#22406424)

It definitely is not orthogonal. Suppose an OS thread goes into an infinite loop. How do you cleanly stop it (feel free to assume Linux/Windows/MacOS)?. In Erlang this is possible because of the custom threading implementation.

[ Parent | on HN ]

Re:Bastion – Highly-available distributed fault-tolerant run... by blattimwind on Monday February 24, 2020 @01:06PM (#22406530)

In Erlang that's possible because the program runs in a VM. Erlang could do the same with 1:1 and m:1 threading.

[ Parent | on HN ]

Re:Bastion – Highly-available distributed fault-tolerant run... by zzzcpan on Monday February 24, 2020 @01:06PM (#22406525)

It's because of the vm interpreter that calls into the scheduler within loop iterations. Nothing to do with threads.

[ Parent | on HN ]

Re:Bastion – Highly-available distributed fault-tolerant run... by chrisseaton on Monday February 24, 2020 @03:00PM (#22407822)

> How do you cleanly stop it

The JVM manages this - there are many options:

- reading a flag - patching the running - changing memory protection and causing a segfault

[ Parent | on HN ]

Re:Bastion – Highly-available distributed fault-tolerant run... by saagarjha on Monday February 24, 2020 @01:21PM (#22406707)

> Suppose an OS thread goes into an infinite loop. How do you cleanly stop it (feel free to assume Linux/Windows/MacOS)?

ptrace it?

[ Parent | on HN ]