A force stop option

Answered

Follow

Morten Frellumstad

• November 10, 2022 14:32

Sometimes you have a misbehaving system. Stopping pipes with stop button and starting again works some time. Stop signal (stop button) is not intrusive, it waits its turn, so if its stuck waiting for an answer that does not come the stop will never be acted upon. Now forcefully restarting subnode is only option. But this is not something for "normal" users. A forceful stop option would be a good option for this. E.g. in form of a dropdown alternative for stop button.

0

• Official comment

  

  Geir Ove Grønmo

  • March 03, 2023 12:03

  Interruption of threads is cooperative in most programming languages. That means that the thread will actually have to check if it has been interrrupted, and if it has then stop. Unfortunately a lot of what the pipes do are blocking I/O which means that there is no way that they can be interrupted other than waiting for a timeout (if it has been set). If it was possible to do cooperative interruption then we would have done this by default everywhere, but that is unfortunately not how it is today in every supported system. That means that one are left with two options: 1) shorter timeouts, or 2) use the force restart endpoint of the worker node (which will forcefully exit the process).

  Comment actions Permalink

Please sign in to leave a comment.