为什么我们要对zabbix的数据库进行分区呢,因为随着时间的推移,数据库的表越来越大,这样一来,我们的查询效率就很低了,对此为了方便我们查询,我们有必要对zabbix数据库进行分区
我们可以去查看我们的MySQL的表的大小
这个写的挺详细的,适合小白
然后开始我们的分区
-
使用truncate命令清空zabbix 所有监控数据
-
先进入mysql –uzabbix –pZ@bbix@123
-
use zabbix;
-
show tables;
truncate table history; optimize table history; truncate table history_str; optimize table history_str; truncate table history_uint; optimize table history_uint; truncate table trends; optimize table trends; truncate table trends_uint; optimize table trends_uint; SET FOREIGN_KEY_CHECKS=0; truncate table events; SET FOREIGN_KEY_CHECKS=1; optimize table events;
注意:这些命令会把zabbix所有的监控数据清空,只是清空监控数据,添加的主机,配置,拓扑图不会丢失。如果对监控数据比较看重的话注意备份数据库
truncate是删除了表,然后根据表结构重新建立。
-
创建sql文件
vim partition.sql
DELIMITER $$ DROP PROCEDURE IF EXISTS `partition_create`$$ 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 $$ DROP PROCEDURE IF EXISTS `partition_drop`$$ 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 $$ DROP PROCEDURE IF EXISTS `partition_maintenance`$$ 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 $$ DROP PROCEDURE IF EXISTS `partition_verify`$$ 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 ; DELIMITER $$ DROP PROCEDURE IF EXISTS `partition_maintenance_all`$$ CREATE PROCEDURE`partition_maintenance_all`(SCHEMA_NAME VARCHAR(32)) BEGIN CALL partition_maintenance(SCHEMA_NAME, 'history', 90, 24, 14); CALL partition_maintenance(SCHEMA_NAME, 'history_log', 90, 24, 14); CALL partition_maintenance(SCHEMA_NAME, 'history_str', 90, 24, 14); CALL partition_maintenance(SCHEMA_NAME, 'history_text', 90, 24, 14); CALL partition_maintenance(SCHEMA_NAME, 'history_uint', 90, 24, 4); CALL partition_maintenance(SCHEMA_NAME, 'trends', 730, 24, 14); CALL partition_maintenance(SCHEMA_NAME, 'trends_uint', 730, 24, 14); END$$ DELIMITER ;
说明:
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:本次一共生成多少个分区
例如:
CALL partition_maintenance(SCHEMA_NAME, ‘history’, 90, 24, 14);
这个例子表示history表最多保存90天的数据,每隔24小时生成一个分区,这次一共生成14个分区
保存退出之后,执行以下命令
导入存储过程到zabbix中
mysql -uzabbix -pZ@bbix@123 zabbix < partition.sql
执行存储过程
mysql -uzabbix -pZ@bbix@123 zabbix -e “CALL partition_maintenance_all(‘zabbix’)” &>
/var/log/partition.log&
执行结束之后进入我们的MySQL查看我们有没有分区成功
mysql –uroot –p
password
use zabbix;
show create table history;
如果出现有很多个partition就说明我们分区成功了
分区成功后我们再添加计划任务
[root@zabbix ~]# crontab -e
#/opt/mysql/mysql-5.7.31/bin/mysql这里指的是你数据库的运行路径,要填自己的路径别填错了
01 01 * * * /opt/mysql/mysql-5.7.31/bin/mysql -uzabbix -p Z@bbix@123 zabbix -e"CALL partition_maintenance_all('zabbix')" &>/var/log/partition.log
[root@zabbix ~]# crontab -l
这样就说明我们的定时任务添加完毕
提示:因为存储过程会老化,比如上面所说history表最多保存28天的数据,每隔24小时生成一个分区,这次一共生成14个分区,当生成第15个分区时存储过程就已经老化了,后面的监控数据就存储不了,会存在丢失监控数据,所以,需要定时执行调用存储过程。设置定时任务时间是通过每24小时会产生一个分区,这次一共生成14个分区,也就是说第15天就存储过程就会老化,那我们就设定每天1点调用存储过程创建一次(只要在14天以内的时间都允许)。
怎么删除指定分区历史数据,这点我们首先先获取我们想要删除的时间段,把它转化为时间戳
date -d $(date -d “-30 day” +%Y%m%d) +%s
DELETE FROM tb WHERE CreateTime>=‘2017-01-01 00:00:00’ AND CreateTime<=‘2017-02-01 00:00:00’ (删除指定时间,某一个时间段)
DELETE FROM tb WHERE CreateTime BETWEEN ‘2017-01-01 00:00:00’ AND ‘2017-02-01 00:00:00’(删除指定时间,某一天)
然后把得到的时间戳带入你的MySQL语句中,
先进去MySQL
mysql -uroot -p
use zabbix;
delete from history where ‘clock’ < 1614355200;
optimize table history;
delete from history_str where ‘clock’ < 1614355200;
optimize table history_str;
delete from history_uint where ‘clock’ < 1614355200;
optimize table history_uint;
delete from trends where ‘clock’ < 1614355200;
optimize table trends;
delete from trends_uint where ‘clock’ < 1614355200;
optimize table trends_uint;
delete from events where ‘clock’ < 1614355200;
optimize table events;