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
constpublisherQueue=newBeeQueue(queueName,isWorker: false,redis,activateDelayedJobs: true,});constconsumerQueue=newBeeQueue(queueName,{isWorker: true,
redis,removeOnSuccess: true,});consumerQueue.process(3,async(job)=>{logger.debug('Job starting',{jobId: job.id,jobData: job.data,queueName: queue.name,});});// on receiving SIGTERM, i runawaitconsumerQueue.close(TIMEOUT)// TIMEOUT set to 90 secs
I have a simple set up as above.
It seems that the .close has zero impact on my workers, as they continue running. (I know this as my workers continue logging after the .close() call)
On every shutdown i basically get a error from bee-queue saying :"Operation timed out."
Is there something wrong with my set up? or is there an issue with .close() ?
(i couldnt find anything obvious in the source code)
The text was updated successfully, but these errors were encountered:
@compwright Unfortunately, I am unable to reproduce this error. After closing the queue worker stops processing new messages as expected. @fahyik Can you maybe provide a more detailed question. Your redis version, node version etc. Might be related to that.
I have a simple set up as above.
It seems that the .close has zero impact on my workers, as they continue running. (I know this as my workers continue logging after the .close() call)
On every shutdown i basically get a error from bee-queue saying :"Operation timed out."
Is there something wrong with my set up? or is there an issue with
.close()
?(i couldnt find anything obvious in the source code)
The text was updated successfully, but these errors were encountered: