You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all. I am currently in the process of migrating BullJS to BullMQ and finished everything so far. Processing looks like it's done before. The only thing I'm wondering about is the amount of open Redis connections. They seem to ramp up and stay (orphaned) once a job finished. In our scenario, majority of the workers are sandboxed and we have a handful of scheduled jobs.
Now to the key question: Is there a recommended way to handle finished workers? In the bundled tests I see, that all instances (Queue, QueueEvent and Worker) have a function "close(force: boolean)" ... Should we close them, once a worker finished?
Any recommendation is appreciated. Thanks in advance.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi all. I am currently in the process of migrating BullJS to BullMQ and finished everything so far. Processing looks like it's done before. The only thing I'm wondering about is the amount of open Redis connections. They seem to ramp up and stay (orphaned) once a job finished. In our scenario, majority of the workers are sandboxed and we have a handful of scheduled jobs.
Now to the key question: Is there a recommended way to handle finished workers? In the bundled tests I see, that all instances (Queue, QueueEvent and Worker) have a function "close(force: boolean)" ... Should we close them, once a worker finished?
Any recommendation is appreciated. Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions