-
Notifications
You must be signed in to change notification settings - Fork 8
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
stream-loader and url-fetcher can become unresponsive #202
Comments
I think I've observed StreamLoader getting stuck when the unit tests run via GitHub actions. smoketest and the GitHub actions both use the same keys, and may be interfering with each other somehow. |
I noticed that SearchLoader ran into a connection reset error and didn't recover from it. From the app.log:
I think SearchLoader should catch these, sleep a little bit, and requeue. |
The other one that needs to be caught in the StreamLoader:
|
I've noticed on smoketest that after long periods of time (days) the stream-loader and url-fetcher can sometimes start to fail to pick up new jobs from Redis--but are still running. I think that this is happening because the event loop inside of each type of job needs to log and catch when an exception occurs. I think we need to look specifically at UrlFetcher, VideoFetcher, StreamLoader and SearchLoader.
The text was updated successfully, but these errors were encountered: