Ad Widget

Collapse

Zabbix Upgrade 2.2 to 3.0 with MySQL Partitioning

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • yuusou
    Junior Member
    • Feb 2014
    • 24

    #1

    Zabbix Upgrade 2.2 to 3.0 with MySQL Partitioning

    I'm currently running Zabbix 2.2 with the history and trend tables partitioned.
    I done the partitioning using the first guide that was on the wiki (Docs/howto/mysql partitioning).
    Note I'm running Percona XtraDB Cluster (Galera) 5.6 with Zabbix as a high-available active-passive setup (2 nodes + Galera arbitrator).

    I'm planning to upgrade Zabbix to 3.0 but I'm worried about the changes in the tables that could take too long (history table has over 500 million rows, each partition not so much, 440NVPS) or could break the database due to the partitioning.

    Has anyone done this upgrade? What was the impact on the database level? Do the history and trend tables change?
  • sabyr_almaz
    Junior Member
    • Jul 2013
    • 1

    #2
    Hi yuusou!

    I have similar situation now but without partitioning and with Three Master Percona XtraDB Cluster, and need to upgrade from 2.4 to 3.4 with database of 160GB data.
    Was your upgrade successfull?

    Comment

    • kloczek
      Senior Member
      • Jun 2006
      • 1771

      #3
      There is no known problems on use partitioned tables and upgrade between major versions.
      http://uk.linkedin.com/pub/tomasz-k%...zko/6/940/430/
      https://kloczek.wordpress.com/
      zapish - Zabbix API SHell binding https://github.com/kloczek/zapish
      My zabbix templates https://github.com/kloczek/zabbix-templates

      Comment

      Working...