41 Upgrade notes for 5.0.31

Improved performance of history syncers

The performance of history syncers has been improved by introducing a new read-write lock. This reduces locking between history syncers, trappers and proxy pollers by using a shared read lock while accessing the configuration cache. The new lock can be write locked only by the configuration syncer performing a configuration cache reload.

Optimized API queries

API database queries, created when searching through names in the hosts and items tables, have been optimized and will now be processed more efficiently. As a result of this change, deterministic triggers need to be created during an upgrade.

On MySQL and MariaDB, this requires GLOBAL log_bin_trust_function_creators = 1 to be set if binary logging is enabled and there is no superuser privileges and log_bin_trust_function_creators = 1 is not set in MySQL configuration file. To set the variable using MySQL console, run:

mysql> SET GLOBAL log_bin_trust_function_creators = 1;

Once the upgrade has been successfully completed, log_bin_trust_function_creators can be disabled:

mysql> SET GLOBAL log_bin_trust_function_creators = 0;

Triggers are also created for PostgreSQL and Oracle database.

Query separate tablespaces in Oracle databases with Zabbix agent 2

The following Zabbix agent 2 items, supported for the Oracle plugin, now have additional optional parameters:

• oracle.diskgroups.stats[<existingParameters>,<diskgroup>]
• oracle.archive.info[<existingParameters>,<destination>]
• oracle.cdb.info[<existingParameters>,<database>]
• oracle.pdb.info[<existingParameters>,<database>]
• oracle.ts.stats[<existingParameters>,<tablespace>,<type>]

These parameters allow to query separate instances of data instead of all data, thus improving performance.