Manuel Astudillo
Manuel Astudillo
Possible Memory Leak - heapdumps show continuous growth in compiled code being retained by dummy job
Now, there could be a leak, but it is too small to be debugged unfortunately. This is the state of NodeJS ecosystem, some leaks you must live with as long...
Possible Memory Leak - heapdumps show continuous growth in compiled code being retained by dummy job
Reopened in case the author can provide more evidence.
I think you need to instantiate the connection first with Redis.Cluster and pass that to the Queue and Worker constructors. Also, you must use {} on the queue prefix, something...
The best would be to request such feature if not available already in the nestjs/bull repo: https://github.com/nestjs/bull
@flipswitchingmonkey yes, the same in BullMQ except you pass a IORedis instance as a connection property instead of a "createClient" callback.
Thats a good question actually. We merged a PR with this change not so long ago but I do not remember the underlying reason: https://github.com/taskforcesh/bullmq/commit/a053d9b87e9799b151e2563b499dbff309b9d2e5
Unless I am missing something, what you are actually requesting is that in simple deduplication mode we do not deduplicate if the job is already in active status. If this...
> Current behaviour is "a job completes at least once after it is scheduled". > > What I need is "a job starts and completes at least once after it...
Btw, I think that if you had a deploymentId that is unique for every deployment that actually starts, that would for the most part do what you want, if you...
The difficulty with this feature relies in avoiding the same job running in parallel, in general it will only work as designed for 1 worker with concurrency 1.