[BUG/FEAT] When a runner is removed, it should shut down / shut down after a number of failures #147

New issue

Open

opened 2024-01-21 09:13:25 +00:00 by voltagex · 1 comment

voltagex commented

2024-01-21 09:13:25 +00:00

I removed a runner from the UI and forgot about it. I then noticed the runner binary was still running, logging fairly regularly

...
ERRO[2024-01-21T20:08:47+11:00] failed to fetch task error="unavailable: 502 Bad Gateway"
ERRO[2024-01-21T20:08:49+11:00] failed to fetch task error="unavailable: 502 Bad Gateway"
ERRO[2024-01-21T20:08:51+11:00] failed to fetch task error="unavailable: 502 Bad Gateway"
...

(cut out 10x the amount of logs for this example)

I think there should be a configurable retry, after which the runner shuts down, or at least a backoff.

I removed a runner from the UI and forgot about it. I then noticed the runner binary was still running, logging fairly regularly ``` ... ERRO[2024-01-21T20:08:47+11:00] failed to fetch task error="unavailable: 502 Bad Gateway" ERRO[2024-01-21T20:08:49+11:00] failed to fetch task error="unavailable: 502 Bad Gateway" ERRO[2024-01-21T20:08:51+11:00] failed to fetch task error="unavailable: 502 Bad Gateway" ... ``` (cut out 10x the amount of logs for this example) I think there should be a configurable retry, after which the runner shuts down, or at least a backoff.