-
Change Request
-
Resolution: Duplicate
-
Critical
-
None
-
2.2.0
-
CentOS 6.4
MySQL 5.5.34-32.0 (Percona Server)
Nginx 1.0.15 / php-fpm 5.3.3 with eAccelerator
Forum thread: https://www.zabbix.com/forum/showthread.php?t=43096
After upgrading to 2.2.0 i had very big problems when trying to show values within the "latest data" section. At the end MySQL DB crashes sooner or later because it hasn't enough RAM. This worked fine all the time, never had any problems with older versions. Even increasing RAM doesn't help anything.
An example:
I'm opening Latest data section. Group "one" is open, it has four hosts with around 35-40 checks each. Fine. Selecting another host of the group sometimes takes around 10 seconds to loaded. Was much less than one second before. Loaded one time, it seems to be fast again. At least for some time.
OK, lets switch to another group. Group "two", three devices, 16 items each. Takes 8 seconds to load, less than one before the upgrade... Most often it doesn't even switches to the new group, but jumps back to the one which was selected before.
Next group. Now it's getting interesting... Cisco switches, three of them, around 2600 checks all together (yes, 2600...).
RAM of the MySQL Process jumps from ~9% to ~50% (1.8g), CPU at 100%. RAM keeps growing slowly. CPU comes down after some minutes. No values shown at all...
Switching to another group and back to the Cisco switches. Same behaviour as before, RAM jumps from 55% to 87% (3.3g), system starts to swap. If i do this one more time now, MySQL crashes and restarts...
Worked amazingly fine with 2.0.9 and 2GB RAM before, and now, with 2.2.0 it's not. Even if i double the RAM. Very very strange...
Any help would be appreciated.
Urs
- duplicates
-
ZBX-7373 Very slow SQL query for getting last values from history and sometimes can be finished with error
- Closed