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

The count of completed job always is 1800 #876

Closed
Peatechen opened this issue Nov 15, 2021 · 4 comments
Closed

The count of completed job always is 1800 #876

Peatechen opened this issue Nov 15, 2021 · 4 comments

Comments

@Peatechen
Copy link

The count of completed job always is 1800 when use getJobCounts

@manast
Copy link
Contributor

manast commented Nov 15, 2021

@Peatechen Is it possible that you are using "removeOnComplete" with a value of 1800? If that is the case, then thats why. However I agree that it could be useful to know all the completed jobs ever and get that as a count too.

@Peatechen
Copy link
Author

@Peatechen Is it possible that you are using "removeOnComplete" with a value of 1800? If that is the case, then thats why. However I agree that it could be useful to know all the completed jobs ever and get that as a count too.

As you said,I have set removeOnComplete: ms("30m") / 1000

@JCMais
Copy link

JCMais commented Jan 24, 2024

I suppose queue.getMetrics does not have this issue right? as it does not use the value from the list of jobs, instead it uses from internal metrics data structure

@Peatechen
Copy link
Author

I suppose queue.getMetrics does not have this issue right? as it does not use the value from the list of jobs, instead it uses from internal metrics data structure

Sorry, my mistake, I misunderstood the 'removeOnComplete' parameter and thought it was a parameter for delayed deletion.

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

3 participants