-
Notifications
You must be signed in to change notification settings - Fork 163
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
Stalled Jobs #21
Comments
Hey Jordan, Humm, that's odd, I haven't seen anything like that. First thing may be to try to figure out where the workers are stalling. Are the jobs not completing (no "done" log entry if you're using the logging middleware)? The second would definitely be something I'd want to look into. If you can extract the smallest amount of code that reproduces the issue, please post it here so I can help dig into the problem. Cheers, |
I got similar behavior with ruby workers when they just go out of memory. Probably same here. |
Closing for lack of actionable info. Feel free to reopen if that changes. |
I have two instances of go-workers running on a couple vps servers (1GB ram -> 25 workers) and (3GB ram -> 40 workers ) that simply go out to queued urls and does some light scraping.
They start out great but quickly stall making no more progress. I don't see any errors my logs, just the last item pulled from the queue, the processes remain running, just no more progress being made.
Any suggestions on ways to debug this?
The text was updated successfully, but these errors were encountered: