CMON Logs QuestionsCompleted
currently I'm wondering why the cmon-folder located under /var/lib/mysql/cmon has a size of 3.7 Gigs.
After checking the table files (*.ibd) in the cmon folder I saw that the log file "cmon_host_log.ibd" actually has a size of 2.4Gig. I checked the Cluster Control Web Interface for particular logs but could not find any log files which show me information about the cmon_host_log.
So my questions are:
- Is there a specific reason why the "cmon_host_log.ibd" has a size of 2.4 Gig while logs like cmon_stats_daily.ibd (which seem to be more important) are smaller with a size of 300MB?
- Can the host log be reduced?
If you are missing some information please let me know.
Thanks a lot.
The cmo_host_log carries the logs of your database nodes and stores into that table which means, if you have lots of verbose logs from your db nodes (error logs), then that means it can increase faster in due time compared to cmon_stats_daily table.
If you want to be reduced, one way I only see for now is to manually login to mysql and delete records to that table but you must need to stop the cmon service (run command `service cmon stop`) and run a null alter to table cmo_host_log ( i.e. ALTER TABLE cmo_host_log ENGINE=InnoDB) to reclaim the space and decrease the file size of the table.
For the meantime, our dev sees this and have filed internal Jira for improvement on this issue.
Thanks for bringing up this Oliver.
Please sign in to leave a comment.