Skip to content
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

Closed
cktang88 opened this issue Sep 19, 2020 · 6 comments
Closed

Feature parity vs bull v3 #274

cktang88 opened this issue Sep 19, 2020 · 6 comments

Comments

@cktang88
Copy link

How does this compare feature wise with the current https://github.com/OptimalBits/bull ?
Is there a roadmap for features?

@manast
Copy link
Contributor

manast commented Sep 21, 2020

On the top of my head I think only TTL for jobs is missing on BullMQ.

@mgan59
Copy link

mgan59 commented Oct 8, 2020

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 TTL set. Also saw issue #85 mentioned. Wanted to clarify if I need to enable something on my end or if it isn't implemented completely?

@manast
Copy link
Contributor

manast commented Oct 8, 2020

@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

@mgan59
Copy link

mgan59 commented Oct 8, 2020

@manast aahh perfect, thanks for clarifying. And the link to the document. This helps a bunch and should solve my key buildup. 👍

@manast manast closed this as completed Oct 8, 2020
@adamreisnz
Copy link

@manast any progress on the TTL feature?

@manast
Copy link
Contributor

manast commented Aug 6, 2021

@adamreisnz I created a new issue for it: #677

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants