sql opennebula.logdb table grows indefinitely in solo mode
|Assignee:||Ruben S. Montero||% Done:|
|Category:||Core & System|
|Target version:||Release 5.4.3|
|Affected Versions:||OpenNebula 5.4, OpenNebula 5.4.1, OpenNebula 5.4.2|
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?
B #5432: Execute timer action for SOLO oned's, this clean federation log
in non-HA configurations
#4 Updated by Laurence Gill about 3 years ago
Ruben S. Montero wrote:
Fix now in one-5.4 and master
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.