Kryptronic Software Support Forum
You are viewing this forum as a guest. Login to an existing account, or create a new account, to reply to topics and to create new topics.
#1 02-07-2020 04:05:18
- sdn
- Member
- From: UK
- Registered: 05-29-2007
- Posts: 882
K9 Server Memory Requirement
Munin is reporting a critical error with "MySQL InnoDB free table space" on all graphs maxed out at 8.0M and average 6.97M on the year graph.
Our dedicated server spec is
Platform: Linux
Operating System: CentOS 7 64-bit
Control Panel: cPanel Pro
CPU: 1x Intel Xeon E3-1230v5 @ 3.4GHz
Memory: 2x 8GB DDR4 U
Hard Drive: 2x 120GB SSD RAID1
Can you advise how we can rectify the error?
Would having a clearout of the DB help and if so how to do that?
I have asked our webhost to advise as well.
Last edited by sdn (02-07-2020 04:15:58)
Simon
Offline
#2 02-07-2020 04:32:27
- sdn
- Member
- From: UK
- Registered: 05-29-2007
- Posts: 882
Re: K9 Server Memory Requirement
Our webhost has replied as follows:
This is a known issue with Munin and the way it interacts with MySQL and InnoDB.
Munin throws a warning whenever there is >2GB of table space and a critical warning at >1GB tablespace remaining.
MySQL defaults to creating a 10MB auto-expanding tablespace ( this can be verified with # mysql -e "SHOW VARIABLES LIKE 'innodb_data_file_path'"
This means InnoDB will perpetually show <10MB of space (resulting in a permanent Munin warning) yet will always seamlessly autoextend as needed.
The way to resolve is for us to simply to disable the alerts through creation of this file:
# vi /etc/munin/plugin-conf.d/mysql_innodb
And placing the following inside
[mysql_innodb]
env.warning 0
env.critical 0
Simon
Offline
#3 02-07-2020 09:09:05
Re: K9 Server Memory Requirement
Thanks for the follow-up. To safely clear space in the database by removing old sessions and carts, execute these commands:
Code:
DELETE FROM ecom_cart DELETE FROM core_sessions
FYI: Versions 9.0.2 are very highly optimized in regard to database storage requirements that I doubt you'll find any tables you think are too large. On busy sites we were seeing the core_sessions table expand to over 1 million rows over time and maintaining that level due to the way V8 pruned old entries. The same sites using K9 (9.0.2+) are seeing that same table at 150k rows with four times the traffic. So make sure you're on 9.0.2+, which I believe you are.
Nick Hendler
Offline