-
Notifications
You must be signed in to change notification settings - Fork 248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
generic worker didn't handle a failure to register well #6963
Comments
Thanks for adding this, this looks interesting!
I wonder why it wasn't considered a zombie (#6333) and was killed before No traces of such instance in logs. One likely explanation is that by the time that worker tried to register it was already removed from the database after So when this happens on the services side, worker should be shutting itself down instead of trying to re-register |
It doesn't appear as though there's some limit on the number of unsuccessful |
I came across an instance today that's been up for 6 days doing no work. Digging into the logs I found:
...and the
dead -> failed
messages continue perpetually.I would've expected that either that worker eventually successfully comes up, or shuts itself down after some amount of time.
The text was updated successfully, but these errors were encountered: