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

log table growth #737

Closed
ixcat opened this issue Feb 25, 2020 · 1 comment
Closed

log table growth #737

ixcat opened this issue Feb 25, 2020 · 1 comment

Comments

@ixcat
Copy link
Contributor

ixcat commented Feb 25, 2020

Somewhat a 'discussion' ticket than a concrete issue for the moment -

User mentioned large log tables resulting from continuous background workers -
While cleanup is fairly straightforward, it might make sense to:

a) Have some control of logging of jobs to log table

b) Have some facility for auto or periodic cleanup according to some parameters

Also: it was noted that many entries related to deleting autopopulate keys from the jobs table were primarily the source of the log growth. Since these particular entries don't relate directly to user data deletion, it might make sense to disable logging them to slow the log table growth.

@dimitri-yatsenko
Copy link
Member

dimitri-yatsenko commented Feb 27, 2020

ok, let's just skip logging operations on the jobs table or any of the auxiliary tables.

guzman-raphael added a commit that referenced this issue Apr 14, 2020
Fix #737: Avoid logging events on auxiliary tables such as ~jobs, ~log, etc.
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

2 participants