Bull is a Node library that implements a fast and robust queue system based on redis. It is the recommended successor to Automattic's deprecated Kue. The next version of Bull, currently in development, is BullMQ.
Questions tagged [bull]
100 questions
1
vote
1 answer
How to Use Heroku Background Workers with NestJS and Bull?
What is the recommended way of providing Heroku workers for heavy processes that I want running on my queue using NestJS?
I have an HTTP server running on Heroku that executes certain time-consuming tasks (e.g. communicating with certain third-party…
MegaSpaceHamlet
- 113
- 6
1
vote
0 answers
Job does not get picked up by worker in bullmq
I a using bullmq with ioredis in an express server. I have about 5 queues for different tasks. But none of the jobs seem to be getting picked up by workers.
I have checked the redis connections, and possible typoes in the queue names. What am I…
The_C1oud
- 11
- 1
- 1
1
vote
1 answer
BullMQ - add jobs to queues from different service to worker
I'm trying to figure out the best architecture for a scalable BullMQ implementation. We have a number of different services that are going to be feeding jobs into queues. In some situations we may have multiple different services feeding jobs into…
oldo.nicho
- 2,149
- 2
- 25
- 39
1
vote
2 answers
Why is @nestjs/bull not able to connect to Heroku Redis?
This works for local redis-server
BullModule.forRoot({
redis: {
host: "localhost",
port: 6379,
db: 0,
password: ""
}
})
But if I use the DataStore Credentials on Heroku Redis, the bull board does not load and…
NovemberSpawn
- 73
- 1
- 6
1
vote
0 answers
key distribution is not correct in bull redis cluster
I have around 16 queues, which are being used for delayed jobs.
Some queues are used multiple times, In a one-time slot, there are some queues which are being used around 50 times and the rest are 3 to 4 times.
Implementation examples:-
import Bull…
Shivam Raj
- 23
- 5
1
vote
0 answers
Cron Jobs in NestJS schema-based multitenancy application using TypeORM and Bull
In my application there are several "partners", where each one is a tenant. Is there any way for each partner to perform the same jobs at the same scheduled time using Bull repeat option? Example: all partners every day at 8 AM must perform the…
Eric Serka
- 11
- 1
1
vote
0 answers
NodeJS with Bull: Cant run job / queue twice, getting : Error: Cannot define the same handler twice __default__
I created a job that allows me to create a pdf file with dynamic content inside. It works when I do a post request the first time and start the job, but the second time it fails with the errror above.
what I basically have in the invoiceWorker.ts…
codingIsLove
- 101
- 1
- 8
1
vote
1 answer
Bull job not getting triggered in cron[Node.js]
I have multiple background jobs processors set up using the bull package like below
import { CronJob } from 'cron';
import Queue from 'bull';
let queue = new Queue('workers', {
// settings: { lockDuration: 60 * 20000 },
defaultJobOptions:…
nipek
- 810
- 1
- 9
- 22
1
vote
0 answers
In which way Node.js handles jobs in parallel? [Bull v3]
I have started experimenting in Node.js lately.
I'm currently setting up an app, which will handle multiple queues in parallel by utilising bull library, to run heavy jobs in the background.
I'm looking for an answer, which i hope i did not miss in…
Makis
- 1,214
- 3
- 16
- 40
1
vote
3 answers
how to solve error read ECONNRESET bull library
i got error when i queue with bull library in node js, the error is like this :
Error: read ECONNRESET at TCP.onStreamRead
- - errno: -104,
- - code: 'ECONNRESET',
- - syscall: 'read'
- - }
and
MaxRetriesPerRequestError: Reached…
putu eka mulyana
- 331
- 2
- 9
1
vote
1 answer
Bull job is not stalled when processor terminated only when getting back up
the code that I'm talking about is the repro code linked below
I have 2 "states" in the code (both of them are listening to queue global events):
Add a single message
Listen to messages
For some reason, Bull job is not reported as stalled when…
Raz Luvaton
- 3,166
- 4
- 21
- 36
1
vote
1 answer
How to recover from redis running out-of-memory and crashing due to retained keys by Bull for completed jobs?
It seems that using Bull 3.21.1 as a work queue with default configuration will cause Redis to retain keys indefinitely under successful operation, eventually exhausting memory in Redis and causing a crash. Here is an example experience, described.…
Tim Heilman
- 340
- 2
- 11
1
vote
1 answer
Bulls Queue Performance and Scalability: Queue.add(), Queue.getJob(jobId), Job.remove()
My use case is to create dynamic delayed job. (I am Using Bulls Queue which can be used to create delayed Jobs.)
Based on some event add some more delay to the delayed interval (further delay the job).
Since I could not find any function to update…
Mohd Waseem
- 1,244
- 2
- 15
- 36
1
vote
1 answer
bull queue block job while got job on different function
I need an approach to block worker to process a job while I called getJob on different function. I've looked around but couldn't find a solution for that.
I have following setup.
In nodeJS with express, I have worker node.
Job created with delayed…
Nasantogtokh Amarsaikhan
- 116
- 1
- 9
1
vote
0 answers
Duplicated queue jobs when running service in cluster
I'm new to working with distributed queue systems, so I guess my question may be weird. But really hope to find a solution.
I have a Node.js microservice that uses Bull Queue. The service works with 2 queues: it subscribes on the firstQueue and…
rmshko
- 11
- 2