Manuel Astudillo
Manuel Astudillo
But when this happens, what is the status of the job that could not renew the lock?
How many jobs do you usually run concurrently?
Are these jobs blocking NodeJS event loop? Did you try using sandboxes instead?
@melihplt could it be a bug in NodeJS where the connection enters an infinite loop? Have you tried with a different runtime such as Bun to see if you get...
Why don't you use sandboxed processors which are precisely designed for handling cases where you keep the nodejs event loop busy?
> [@manast](https://github.com/manast) > > I tried this back then with `bull` and ran into huge issues. Since `bull` was an "oldschool" `require()` package, we ran into issues inside our `"type":...
Important here is that you use v5.40+ as there is a know issue before that version that could produce stalled jobs when closing workers gracefully.
@kosiakMD how do you know it is the same issue? you are getting similar errors, but it is not possible to know if what caused the poster issue is what...
I am not sure how this could be improved honestly, unless you sacrifice functionality. Would you define children first and then the parent of those children? In my mind that...
> Quick update on this: It seems like we completely lost connection to Redis at some point or something ... we are on AWS using ElastiCache. Has anyone ever seen...