Bug #5432
sql opennebula.logdb table grows indefinitely in solo mode
| Status: | Closed | Start date: | 10/04/2017 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Ruben S. Montero | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | Release 5.4.3 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 5.4, OpenNebula 5.4.1, OpenNebula 5.4.2 |
Description
Running a federation in solo mode appears to let the logdb table grow to an very large size.
It seems that the cleanup job is only run when HA is configured, so when the server_id is -1 the housekeeping doesn't run. If you set the server_id to 0 so it is a lone master the database is cleaned.
Is this a bug? Should the database not be growing in solo mode, or should the cleaning happen in all modes?
Associated revisions
B #5432: Execute timer action for SOLO oned's, this clean federation log
in non-HA configurations
B #5432: Execute timer action for SOLO oned's, this clean federation log
in non-HA configurations
(cherry picked from commit 577d976d14fa689bbc0cc15ca8d6dbb0eb01588d)
History
#1
Updated by Ruben S. Montero over 3 years ago
- Category set to Core & System
- Status changed from Pending to New
- Assignee set to Ruben S. Montero
- Target version set to Release 5.4.3
- Affected Versions OpenNebula 5.4.1, OpenNebula 5.4.2 added
#2
Updated by Ruben S. Montero over 3 years ago
Yes I can confirm this is a bug, cleaning should happen in all modes. The log is used to sync the federated instances also.
#3
Updated by Ruben S. Montero over 3 years ago
- Status changed from New to Closed
- Resolution set to fixed
Fix now in one-5.4 and master
#4
Updated by Laurence Gill over 3 years ago
Ruben S. Montero wrote:
Fix now in one-5.4 and master
Excellent thanks.
Is it safe to truncate this table? It has grown so large the clean up job does not complete within a sensible amount of time. It took several hours to manually batch delete the old data, but a second instance is much larger.
Thanks