-
Notifications
You must be signed in to change notification settings - Fork 43
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
How to clean up the completed job regularly #38
Comments
Hi, The HangfireJobRentionAttribute is not used. |
thank you @perrich. How to set the job's ExpireAt property? I try to set the jobexpireationtimeout at the globalconfiguraiton. (I have to download the src code of hangfire and change the source to remove the 1 hour limit)
|
find out why. InMemory did honor the setting. It is the one by one for loop detele slow the clean up. |
The loop is not done one by one but by 1000 (of one of the managed type). |
Hello,
I have a problem regarding cleanning up the completed job. I tried to use the attribute to define the expiration/life time.
After apply the attribute, I do see the hangfire pick it up in my dashboard. It said that it should be auto delted 28 min ago.
However, I don't see the reduction of the memory footprint of my hangfire application. It keeps going up.
Does MemoryStorage has some build in clean up mechanism like SQL?
https://discuss.hangfire.io/t/does-hangfire-clear-down-old-job-data/2294/2
The text was updated successfully, but these errors were encountered: