-
Notifications
You must be signed in to change notification settings - Fork 359
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
[Bug]: workers stopped consuming job, sometime event loss #2570
Comments
Is it version 1.84.0 ? thats pretty old... also we will need some code to reproduce the issue. |
i have more than 200 type of jobs running in my system, and everything was fine even with the older version. This started happening recently and I haven't made any changes in the code. Earlier I thought, due to unhandled exception node process is killed, but tried to reproduce and no luck. |
|
|
Unfortunatelly this information is not enough for us to be able to perform any further action. Maybe you could start by checking in which statuses the jobs are in right now, verify that all the workers are indeed connected to Redis and so on. |
Version
1.84.0
Platform
NodeJS
What happened?
Sometime experiencing few jobs are not getting processed and sometime no jobs are getting processed, seems happening because of memory issue.
Happening just after the memory spike.
How to reproduce.
No response
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: