-
Notifications
You must be signed in to change notification settings - Fork 218
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
Clean our RUCSS action scheduler jobs periodically without affecting others #4945
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Working as expected
testrail-report-375.pdf
…th default lifespan of 1 hour
881f003
to
a6e111f
Compare
We also added a new filter here to change the cleaner batch size (default value now is 100) wp-rocket/inc/Engine/Common/Queue/RUCSSQueueRunner.php Lines 64 to 73 in 0ed866c
so with each CRON run (every minute), 100 log items will be cleaned. |
We're on v3.11.3 and the rocket_rucss_pending_jobs_cron hook is flooding the actions table. I've checked the source and can see the fix above is in there but it's clearly not working. Looking through the UI in WordPress it currently lists 10 rows per page, each of those 10 rows appear to be created at the same time. This would suggest there are more than 10 jobs being created each minute so I would assume over time cleaning 100 jobs per minute wouldn't be enough? |
Can you plz reach WP Rocket support at |
Will do. Just worked out there have been 19,000+ rows added in the last 15 minutes |
No reply as of yet. |
Description
We needed a way to clean our RUCSS action scheduler jobs after 1 hour without affecting the other jobs from other plugins.
Also added a new filter
rocket_action_scheduler_retention_period
so we can manage the clean lifespan for ours only.Fixes #4940
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Checklist:
Please delete the options that are not relevant.