-
Notifications
You must be signed in to change notification settings - Fork 6
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
Fragility to garbage requests? #84
Comments
Second time in two days, hm.
|
And another:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A bit of a devops open-ended painpoint, even though I am using custom ports there seem to be garbage messages sneaking in such as these HTTP request pieces
I would have to make the dispatcher expect random noise better, unsure how/why that takes it down at the moment. To be precise, the dispatcher process continues to remain functional, but loses connectivity to the workers, which remain stale even though there are available jobs. A dispatcher restart resumes the conversion correctly with the current code.
The text was updated successfully, but these errors were encountered: