zabbix数据库表分区

指尖二进制 • 1 年前 • 855 次点击 • ZABBIX

[TOC]

自我分析：
洪水告警产生的原因是因为没有做过分区表，导致housekeeper执行的时候history表被锁，然而housekeeper执行的时间过长，又导致新数据数据无法录入到history等表，此时history表无法更新同步，监控项还在每5分钟进行检测Agent ping监控项，触发器执行的时候发现最近5分钟没有新数据，导致洪水告警的出现。

针对分析做出的解决方案。做一个表分区。
什么是表分区：表分区是将大表的数据拆分多个小的子集进行存储，一般一天一个分区表。

1：查看数据库是否支持分区

查看是否有此插件“partition”。或者show plugins;查看
发现partition插件已经ACTIVE说明支持分区

MariaDB [(none)]> SELECT PLUGIN_NAME as Name,PLUGIN_VERSION as Version,PLUGIN_STATUS as Status FROM INFORMATION_SCHEMA.PLUGINS WHERE PLUGIN_TYPE='STORAGE ENGINE';
+--------------------+---------+--------+
| Name               | Version | Status |
+--------------------+---------+--------+
| binlog             | 1.0     | ACTIVE |
| MEMORY             | 1.0     | ACTIVE |
| MyISAM             | 1.0     | ACTIVE |
| CSV                | 1.0     | ACTIVE |
| MRG_MYISAM         | 1.0     | ACTIVE |
| InnoDB             | 5.5     | ACTIVE |
| PERFORMANCE_SCHEMA | 0.1     | ACTIVE |
| BLACKHOLE          | 1.0     | ACTIVE |
| ARCHIVE            | 3.0     | ACTIVE |
| Aria               | 1.5     | ACTIVE |
| FEDERATED          | 2.0     | ACTIVE |
| partition          | 1.0     | ACTIVE |
+--------------------+---------+--------+
12 rows in set (0.00 sec)

2：修改mysql数据库表索引

修改表索引zabbix3.2.x以上版本跳过此步

mysql> Alter table history_text drop primary key, add index (id), drop index history_text_2, add index history_text_2 (itemid, id);
Query OK, 0 rows affected (0.49 sec)
Records: 0  Duplicates: 0  Warnings: 0

mysql> Alter table history_log drop primary key, add index (id), drop index history_log_2, add index history_log_2 (itemid, id);
Query OK, 0 rows affected (2.71 sec)
Records: 0  Duplicates: 0  Warnings: 0

3：创建存储过程

--增加分区的存储过程：
DELIMITER $$
CREATE PROCEDURE `partition_create`(SCHEMANAME varchar(64), TABLENAME varchar(64), PARTITIONNAME varchar(64), CLOCK int)
BEGIN
        /*
           SCHEMANAME = The DB schema in which to make changes
           TABLENAME = The table with partitions to potentially delete
           PARTITIONNAME = The name of the partition to create
        */
        /*
           Verify that the partition does not already exist
        */

        DECLARE RETROWS INT;
        SELECT COUNT(1) INTO RETROWS
        FROM information_schema.partitions
        WHERE table_schema = SCHEMANAME AND table_name = TABLENAME AND partition_description >= CLOCK;

        IF RETROWS = 0 THEN
                /*
                   1. Print a message indicating that a partition was created.
                   2. Create the SQL to create the partition.
                   3. Execute the SQL from #2.
                */
                SELECT CONCAT( "partition_create(", SCHEMANAME, ",", TABLENAME, ",", PARTITIONNAME, ",", CLOCK, ")" ) AS msg;
                SET @sql = CONCAT( 'ALTER TABLE ', SCHEMANAME, '.', TABLENAME, ' ADD PARTITION (PARTITION ', PARTITIONNAME, ' VALUES LESS THAN (', CLOCK, '));' );
                PREPARE STMT FROM @sql;
                EXECUTE STMT;
                DEALLOCATE PREPARE STMT;
        END IF;
END$$
DELIMITER ;

--删除分区的存储过程：
DELIMITER $$
CREATE PROCEDURE `partition_drop`(SCHEMANAME VARCHAR(64), TABLENAME VARCHAR(64), DELETE_BELOW_PARTITION_DATE BIGINT)
BEGIN
        /*
           SCHEMANAME = The DB schema in which to make changes
           TABLENAME = The table with partitions to potentially delete
           DELETE_BELOW_PARTITION_DATE = Delete any partitions with names that are dates older than this one (yyyy-mm-dd)
        */
        DECLARE done INT DEFAULT FALSE;
        DECLARE drop_part_name VARCHAR(16);

        /*
           Get a list of all the partitions that are older than the date
           in DELETE_BELOW_PARTITION_DATE.  All partitions are prefixed with
           a "p", so use SUBSTRING TO get rid of that character.
        */
        DECLARE myCursor CURSOR FOR
                SELECT partition_name
                FROM information_schema.partitions
                WHERE table_schema = SCHEMANAME AND table_name = TABLENAME AND CAST(SUBSTRING(partition_name FROM 2) AS UNSIGNED) < DELETE_BELOW_PARTITION_DATE;
        DECLARE CONTINUE HANDLER FOR NOT FOUND SET done = TRUE;

        /*
           Create the basics for when we need to drop the partition.  Also, create
           @drop_partitions to hold a comma-delimited list of all partitions that
           should be deleted.
        */
        SET @alter_header = CONCAT("ALTER TABLE ", SCHEMANAME, ".", TABLENAME, " DROP PARTITION ");
        SET @drop_partitions = "";

        /*
           Start looping through all the partitions that are too old.
        */
        OPEN myCursor;
        read_loop: LOOP
                FETCH myCursor INTO drop_part_name;
                IF done THEN
                        LEAVE read_loop;
                END IF;
                SET @drop_partitions = IF(@drop_partitions = "", drop_part_name, CONCAT(@drop_partitions, ",", drop_part_name));
        END LOOP;
        IF @drop_partitions != "" THEN
                /*
                   1. Build the SQL to drop all the necessary partitions.
                   2. Run the SQL to drop the partitions.
                   3. Print out the table partitions that were deleted.
                */
                SET @full_sql = CONCAT(@alter_header, @drop_partitions, ";");
                PREPARE STMT FROM @full_sql;
                EXECUTE STMT;
                DEALLOCATE PREPARE STMT;

                SELECT CONCAT(SCHEMANAME, ".", TABLENAME) AS `table`, @drop_partitions AS `partitions_deleted`;
        ELSE
                /*
                   No partitions are being deleted, so print out "N/A" (Not applicable) to indicate
                   that no changes were made.
                */
                SELECT CONCAT(SCHEMANAME, ".", TABLENAME) AS `table`, "N/A" AS `partitions_deleted`;
        END IF;
END$$
DELIMITER ;

--维护分区的存储过程：
DELIMITER $$
CREATE PROCEDURE `partition_maintenance`(SCHEMA_NAME VARCHAR(32), TABLE_NAME VARCHAR(32), KEEP_DATA_DAYS INT, HOURLY_INTERVAL INT, CREATE_NEXT_INTERVALS INT)
BEGIN
        DECLARE OLDER_THAN_PARTITION_DATE VARCHAR(16);
        DECLARE PARTITION_NAME VARCHAR(16);
        DECLARE OLD_PARTITION_NAME VARCHAR(16);
        DECLARE LESS_THAN_TIMESTAMP INT;
        DECLARE CUR_TIME INT;

        CALL partition_verify(SCHEMA_NAME, TABLE_NAME, HOURLY_INTERVAL);
        SET CUR_TIME = UNIX_TIMESTAMP(DATE_FORMAT(NOW(), '%Y-%m-%d 00:00:00'));

        SET @__interval = 1;
        create_loop: LOOP
                IF @__interval > CREATE_NEXT_INTERVALS THEN
                        LEAVE create_loop;
                END IF;

                SET LESS_THAN_TIMESTAMP = CUR_TIME + (HOURLY_INTERVAL * @__interval * 3600);
                SET PARTITION_NAME = FROM_UNIXTIME(CUR_TIME + HOURLY_INTERVAL * (@__interval - 1) * 3600, 'p%Y%m%d%H00');
                IF(PARTITION_NAME != OLD_PARTITION_NAME) THEN
                        CALL partition_create(SCHEMA_NAME, TABLE_NAME, PARTITION_NAME, LESS_THAN_TIMESTAMP);
                END IF;
                SET @__interval=@__interval+1;
                SET OLD_PARTITION_NAME = PARTITION_NAME;
        END LOOP;

        SET OLDER_THAN_PARTITION_DATE=DATE_FORMAT(DATE_SUB(NOW(), INTERVAL KEEP_DATA_DAYS DAY), '%Y%m%d0000');
        CALL partition_drop(SCHEMA_NAME, TABLE_NAME, OLDER_THAN_PARTITION_DATE);

END$$
DELIMITER ;

--检查分区、创建第一个分区的存储过程： 
DELIMITER $$
CREATE PROCEDURE `partition_verify`(SCHEMANAME VARCHAR(64), TABLENAME VARCHAR(64), HOURLYINTERVAL INT(11))
BEGIN
        DECLARE PARTITION_NAME VARCHAR(16);
        DECLARE RETROWS INT(11);
        DECLARE FUTURE_TIMESTAMP TIMESTAMP;

        /*
         * Check if any partitions exist for the given SCHEMANAME.TABLENAME.
         */
        SELECT COUNT(1) INTO RETROWS
        FROM information_schema.partitions
        WHERE table_schema = SCHEMANAME AND table_name = TABLENAME AND partition_name IS NULL;

        /*
         * If partitions do not exist, go ahead and partition the table
         */
        IF RETROWS = 1 THEN
                /*
                 * Take the current date at 00:00:00 and add HOURLYINTERVAL to it.  This is the timestamp below which we will store values.
                 * We begin partitioning based on the beginning of a day.  This is because we don't want to generate a random partition
                 * that won't necessarily fall in line with the desired partition naming (ie: if the hour interval is 24 hours, we could
                 * end up creating a partition now named "p201403270600" when all other partitions will be like "p201403280000").
                 */
                SET FUTURE_TIMESTAMP = TIMESTAMPADD(HOUR, HOURLYINTERVAL, CONCAT(CURDATE(), " ", '00:00:00'));
                SET PARTITION_NAME = DATE_FORMAT(CURDATE(), 'p%Y%m%d%H00');

                -- Create the partitioning query
                SET @__PARTITION_SQL = CONCAT("ALTER TABLE ", SCHEMANAME, ".", TABLENAME, " PARTITION BY RANGE(`clock`)");
                SET @__PARTITION_SQL = CONCAT(@__PARTITION_SQL, "(PARTITION ", PARTITION_NAME, " VALUES LESS THAN (", UNIX_TIMESTAMP(FUTURE_TIMESTAMP), "));");

                -- Run the partitioning query
                PREPARE STMT FROM @__PARTITION_SQL;
                EXECUTE STMT;
                DEALLOCATE PREPARE STMT;
        END IF;
END$$
DELIMITER ;

将上面的四个存储过程保存到一个sql文件中进行导入。

[root@zabbix-server ~]# vim partition_call.sql
[root@zabbix-server ~]# mysql -uroot -p123456 zabbix < partition_call.sql

查询zabbix库存储过程是否导入成功

[root@zabbix-server ~]# mysql -uroot -p123456
MariaDB [(none)]> select `name` from mysql.proc where db = 'zabbix' and `type` = 'PROCEDURE';
+-----------------------+
| name                  |
+-----------------------+
| partition_create      |
| partition_drop        |
| partition_maintenance |
| partition_verify      |
+-----------------------+
4 rows in set (0.00 sec)

4：使用存储过程

示例语句：

CALL  partition_maintenance （'<zabbix_db_name>' ， '<table_name>' ， < days_to_keep_data > ， < hourly_interval > ， < num_future_intervals_to_create > ）

zabbix_db_name：库名
table_name：表名
days_to_keep_data：保存多少天的数据
hourly_interval：每隔多久生成一个分区
num_future_intervals_to_create：本次一共生成多少个分区

mysql > CALL partition_maintenance(' zabbix ', 'history', 7, 24, 7);

这个例子就是 history表最多保存7天的数据，每隔24小时生成一个分区，这次一共生成7个分区

统一调用存储过程：

DELIMITER $$
CREATE PROCEDURE `partition_maintenance_all`(SCHEMA_NAME VARCHAR(32))
BEGIN
       CALL partition_maintenance(SCHEMA_NAME, 'history',45,24,45);
       CALL partition_maintenance(SCHEMA_NAME, 'history_log',45,24,45);
       CALL partition_maintenance(SCHEMA_NAME, 'history_str',45,24,45);
       CALL partition_maintenance(SCHEMA_NAME, 'history_text',45,24,45);
       CALL partition_maintenance(SCHEMA_NAME, 'history_uint',45,24,45);
       CALL partition_maintenance(SCHEMA_NAME, 'trends',45,24,45);
       CALL partition_maintenance(SCHEMA_NAME, 'trends_uint',45,24,45);
END$$
DELIMITER ;

将上面存储过程保存sql文件导入。

[root@zabbix-server ~]# vim partition_all.sql
[root@zabbix-server ~]# mysql -uroot -p123456 zabbix < partition_all.sql
[root@zabbix-server ~]# mysql -uroot -p123456
MariaDB [(none)]> select `name` from mysql.proc where db = 'zabbix' and `type` = 'PROCEDURE';
+---------------------------+
| name                      |
+---------------------------+
| partition_create          |
| partition_drop            |
| partition_maintenance     |
| partition_maintenance_all |
| partition_verify          |
+---------------------------+
5 rows in set (0.00 sec)

以后只需要调用这个存储过程就可以了，每天执行一次：
若数据量比较大，首次执行的时间较长，请使用nohup执行（这期间zabbix是无法正常工作的，获取的 agent数据不展示,但数据不会丢失）

[root@zabbix-server ~]# nohup mysql -uroot -p123456 zabbix -e "CALL partition_maintenance_all('zabbix');" &> /tmp/file.txt &

或者登录mysql执行

[root@zabbix-server ~]# mysql -uroot -p123456
MariaDB [(none)]> use zabbix
MariaDB [zabbix]> CALL partition_maintenance_all('zabbix'); # partition_all存储过程的七张表
+--------------------+--------------------+
| table              | partitions_deleted |
+--------------------+--------------------+
| zabbix.trends_uint | N/A                |
+--------------------+--------------------+
1 row in set (1.55 sec)

Query OK, 0 rows affected, 1 warning (1.55 sec)

写成crontab:

# crontab -e
0 1 * * * /bin/mysql -uzabbix -pzabbix zabbix -e "CALL partition_maintenance_all('zabbix');"

5：关闭HouseKeeper

最后关掉Zabbix的HouseKeeper功能：

6：查看数据库是否成功表分区

MariaDB [zabbix]> select TABLE_SCHEMA,TABLE_NAME,PARTITION_NAME from INFORMATION_SCHEMA.PARTITIONS where PARTITION_NAME is not NULL; #每张表都是45个分区。

+--------------+--------------+----------------+
| TABLE_SCHEMA | TABLE_NAME   | PARTITION_NAME |
+--------------+--------------+----------------+
| zabbix       | history      | p202003170000  |    #每张表都是45个分区。
| zabbix       | history_log  | p202003170000  |
| zabbix       | history_str  | p202003170000  |
| zabbix       | history_text | p202003170000  |
| zabbix       | history_uint | p202003170000  |
| zabbix       | trends       | p202003170000  |
| zabbix       | trends_uint  | p202003170000  |
+--------------+--------------+----------------+