Skip to content
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

kafka client warning unable to send to wakeup socket (Endless loop) #1842

Closed
ghost opened this issue Jun 13, 2019 · 5 comments
Closed

kafka client warning unable to send to wakeup socket (Endless loop) #1842

ghost opened this issue Jun 13, 2019 · 5 comments

Comments

@ghost
Copy link

ghost commented Jun 13, 2019

I cannot force close my crawler, it trapped in an endless loop because kafka client warning unable to send to wakeup socket

Screenshot from 2019-06-10 17-01-51

@dpkp
Copy link
Owner

dpkp commented Oct 1, 2019

I believe this is fixed in the latest release, 1.4.7. Please reopen if the issue persists.

@dpkp dpkp closed this as completed Oct 1, 2019
@Prometheus3375
Copy link

Have run into the same issue with version 2.0.1.
Attached log file. I stopped spider by killing its process.

spider.log

@shimon-armis
Copy link

We see a sort of that issue also with version 2.0.2.

@Prometheus3375
Copy link

@shimon-armis look mentioned issue for solution.

@shimon-armis
Copy link

shimon-armis commented Jun 28, 2023

@Prometheus3375 I actually saw it but I still wonder:
Why should we apply the a WA (a suggested here) for each and every consumer app, rather than handling it where it actually happens?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants