Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-17493

Limit trend calculation period for the history regarding housekeeper settings

XMLWordPrintable

    • Team A
    • Sprint 63 (Apr 2020), Sprint 64 (May 2020), Sprint 65 (Jun 2020), Sprint 66 (Jul 2020), Sprint 67 (Aug 2020), Sprint 68 (Sep 2020), Sprint 69 (Oct 2020), Sprint 70 (Nov 2020)
    • 1

      Steps to reproduce:

      1. Zabbix 4.0/4.4 with 0.5TB history and 0.1TB trends with partitioning (MySQL/Percona/MariaDB);
      2. use zabbix_sender/zabbix trapper to gather history from file with timestamps;
      3. send unixtime value equal 0;

      Result:

      1. history syncer stuck doing query:
        select distinct itemid from trends where clock>=0 and itemid in (<very long list of itemids>)
        
      2. MySQL-based DB does not provide global index on partitioned tables - this means full scan for all 365 partitions (trends) due to the requirement get data starting from clock equal 0 even if local indexes are presented for table;

      Problems:

      1. in case of a database partitioning any query trying to get values from the first partition to the last will cause full scan without index;
      2. data with unixtime 0 or out of the defined range useless;

      Expected:

      1. trends should be recalculated only within defined period of time;
      2. drop/not accept history values for the not defined history/trends periods of time;
      3. if possible avoid full scan queries for trends re-calculation in case partitioning is used;

            wiper Andris Zeila
            edgar.akhmetshin Edgar Akhmetshin
            Team A
            Votes:
            6 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: