-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature parity vs bull v3 #274
Comments
On the top of my head I think only TTL for jobs is missing on BullMQ. |
Stumbled into here as I'm getting alerts for my redis memory filling up. Realizing that the Jobs/Keys in redis don't have a |
@mgan59 TTL here does not refer to keys expiration but on TTL for a given job, i.e. if it takes more than TTL to process it should fail. What you should check to avoid filling up your redis instance is the removeOnComplete/removeOnFailed options: https://docs.bullmq.io/guide/jobs/fifo |
@manast aahh perfect, thanks for clarifying. And the link to the document. This helps a bunch and should solve my key buildup. 👍 |
@manast any progress on the TTL feature? |
@adamreisnz I created a new issue for it: #677 |
How does this compare feature wise with the current https://github.com/OptimalBits/bull ?
Is there a roadmap for features?
The text was updated successfully, but these errors were encountered: