Uploaded image for project: 'ZABBIX FEATURE REQUESTS'
  1. ZABBIX FEATURE REQUESTS
  2. ZBXNEXT-2363

DB Schema for MariaDB with TokuDB

    XMLWordPrintable

Details

    • New Feature Request
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 2.2.3, 2.3.1
    • None
    • Proxy (P), Server (S)
    • CentOS 6.5, MariaDB 10.0.12 with latest TokuDB engine

    Description

      We have converted zabbix db from 2.2 to MariaDB with TokuDB.

      Benefits of TokuDB:

      • compression with several levels: we use highest LZMA and got result: InnodDB: 90GB (with partioning, housekeeper sitched off - no defrgamentation) -> TokuDB: 25GB -> bzip2 backup - 5GB
      • no replication lag
      • no locking during backup
      • quick inserts
      • faster queries
      • no fragmentation, no growing db, use housekeeper with no lose performance

      We need special db schema for TokuDB with sevral rules:

      On history tables, there is must only one primary index, but it must be CLUSTERING and COVERING fields item_id, clock
      clustering index it is a table sorted another way, and this index includes all fields of each row, so it is a sorted table

      Trend tables must indexed the same way

      to get more perfomance on select queries some options must be set:

      my.cnf:

      [mysqld]
      optimizer_switch=index_condition_pushdown=off

      query cache must be enabled,
      and event must me created:
      CREATE EVENT flush_query_cache ON SCHEDULE EVERY 5 minute DO FLUSH QUERY CACHE;

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              nucleusv Vadim Nesterov
              Votes:
              6 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated: