-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Burst of "Unable to send to wakeup socket!" #1837
Comments
At first I would suggest replacing
with
just to dig into the issue. |
Hi, i have the same problem...#1842 But after i replace
with
i still get the same error |
ghost
mentioned this issue
Jun 14, 2019
I believe this is fixed in latest release, 1.4.7. Please reopen if issue persists. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After upgrading from 1.4.4 to 1.4.6, we receive a burst of logs of "Unable to send to wakeup socket!".
Based on our metrics, clients are not consuming messages any more.
We solved the issue by restarting our clients.
The text was updated successfully, but these errors were encountered: