Actions
Feature #27971
closedOptimize reports/logs deletion rake task
Difficulty:
Triaged:
Yes
Bugzilla link:
Description
How reproducible:
In customer environments with a lot of content hosts and puppet check-ins
Steps to Reproduce:
1. We had seen customer environments where logs table contain a ton of data with logs table sometimes consuming more than 35GB.
su - postgres c "psql foreman -c \"select count(*) from logs;\""
count
---------
539298
(1 row)
Actual results:
Degradation of Satellite performance since postgres queries too long to finish
Expected results:
Logs table should be cleaned up automatically to keep the number of records at an optimum level - say 50k records.
Additional info:
Updated by The Foreman Bot over 4 years ago
- Status changed from New to Ready For Testing
- Assignee set to Lukas Zapletal
- Pull request https://github.com/theforeman/foreman/pull/7072 added
Updated by Lukas Zapletal over 4 years ago
- Subject changed from Automatic cleanup of logs table to Optimize reports/logs deletion rake task
- Triaged changed from No to Yes
Updated by The Foreman Bot over 4 years ago
- Pull request https://github.com/theforeman/foreman/pull/7241 added
Updated by Lukas Zapletal almost 4 years ago
- Status changed from Ready For Testing to Rejected
These patches were too complex with unclear results, let's focus on refactoring reports storage from scratch.
Actions