Linux – Decrease zabbix server connections to database

linuxpostgresqlzabbix

Is it possible to define a database pool value in order to decrease the database connections sent from zabbix server?

I saw a method when it was done through apache mod_fcgid, Shall it be done with mod mpm_prefork as well?

By doing tests (with only 2 users connected through web gui), I found 60 outgoing connections to database server when my limit in database server was 100, 23 when my limit was 20 (of course it didn't work) and with limit 30 I have 29 outgoing connections, Why such difference?

It seems to me that somehow, zabbix is able to identify the maximum number of database connections to create outgoing connections, but honestly that's a little strange for me, Zabbix seems to abuse of resources when I increase the pool in database server.

The scenario is a shared PostgreSQL server, that's why increasing pools in database server side is not a good idea in my case.

Zabbix is installed in a CentOS 7 server.

Best Answer

Most likely, you are seeing connections from the server. Many server processes will keep their own connection. Making the limits low will cause issues, do not do that - processes will have issues connecting, reconnect, the connections will be opened and closed more often.

Your options are:

Increase the DB connection limit until there are spare connection slots.
Decrease the number of spawned Zabbix server processes (like pollers) until there are spare connection slots.

In general, putting Zabbix DB on a shared resource is not a good idea - that makes your monitoring system unreliable when production load increases or there are any other issues.

Related Solutions

MySQL DB causing high IO running Zabbix server

innodb_buffer_pool_size > 1G, because your dataset size is 1,8GB.

To decrease number of reads you need to increase innodb_buffer_pool_size. To decrease number of writes you need to edit your zabbix templates (disabling some unnecessary items like free inodes, increase intervals between checks).

You have Reads / Writes ratio at 57% / 43%, so enabling Query Cache will not help (it may make things worse, because writes to tables invalidates cache).

Think about increasing tmp_table_size and max_heap_table_size to avoid creating tmp tables on disk (13% of tmp tables). Temporary tables are in MB? it is count? If it is counter, its too high.

Decrease number of connection to 50 (your highest number was 33).

innodb_support_xa = false
innodb_buffer_pool_size = 256M # It depends how many memory is available to MySQL, more is better.
innodb_flush_log_at_trx_commit = 0 # disable writing to logs on every commit and disable fsync on each write
innodb_max_dirty_pages_pct = 90 # avoid flushing dirty pages to disk
innodb_flush_method = O_DIRECT # direct access to disk without OS cache
thread_cache_size = 4
query_cache_size = 0
table_cache = 80? # a little more than number_of_tables_in_zabbix_database

Usefull link about InnoDB optimization.

Linux – zabbix monitoring thesql database

FIXED

{$MYSQL_SOCKET1} = /var/lib/mysql/mysql2.sock

i removed the single quotes from the line and it worked...

Best Answer

Related Solutions

MySQL DB causing high IO running Zabbix server

Linux – zabbix monitoring thesql database

Related Topic