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

filter action scheduler retention period and batch size #24

Merged
merged 6 commits into from
Aug 15, 2024

Conversation

circlecube
Copy link
Member

Proposed changes

We identified an issue where the action scheduler tables used by WooCommerce and other plugins accumulate an excessive amount of data, sometimes reaching up to 20 GB. This is because expired actions are retained in the database for 30 days by default, allowing the table size to grow uncontrollably, even reaching 100 GB in some cases.

As a quick and straightforward fix, this PR changes the default retention period from 30 days to 5 days. This adjustment should significantly reduce the table size and prevent database bloat without requiring extensive code changes.

See ticket PRESS0-2085

Type of Change

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update (if none of the other choices apply)

Video

Checklist

  • I have read the CONTRIBUTING doc
  • I have viewed my change in a web-browser
  • Linting and tests pass locally with my changes (My changes are good, but don't have time to update the whole file with docs. I made the easy fixes.)
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

Further comments

@chrisdavidmiles chrisdavidmiles changed the title add filter for action scheduler retention period filter action scheduler retention period and batch size Aug 15, 2024
@wpalani wpalani merged commit ed7db2c into main Aug 15, 2024
7 checks passed
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

Successfully merging this pull request may close these issues.

4 participants