树莓派可以做网站的服务器吗,网站建设与设计ppt,如何选择网站域名,招聘信息网站ZABBIX监控设备较多的时候#xff0c;Mysql数据库容易成为性能的瓶颈#xff0c;可以通过数据库分表的方式来进行优化。步骤如下#xff1a; 一、停用zabbix服务
# 避免修改分区表时#xff0c;数据还有写入
systemctl stop zabbix
二、备份MySQL zabbix DB
避免修改分… ZABBIX监控设备较多的时候Mysql数据库容易成为性能的瓶颈可以通过数据库分表的方式来进行优化。步骤如下 一、停用zabbix服务
# 避免修改分区表时数据还有写入
systemctl stop zabbix
二、备份MySQL zabbix DB
避免修改分区表后各类异常以便回滚
# 备份db:
mysqldump -h127.0.0.1 -P3306 -uroot -pPssw0rd1234 --single-transaction --default-character-setutf8 -R -E zabbix --log-error/usr/tmp/zabbix0323.log /usr/tmp/zabbix0323.sql
三、进入mysql数据库输入脚本
mysql -uroot -p
以下为脚本内容 use zabbix;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__interval1; SET OLD_PARTITION_NAME PARTITION_NAME; END LOOP;SET OLDER_THAN_PARTITION_DATEDATE_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 dont want to generate a random partition * that wont 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 $$
CREATE PROCEDURE partition_maintenance_all(SCHEMA_NAME VARCHAR(32))
BEGIN CALL partition_maintenance(SCHEMA_NAME, history, 90, 24, 7); CALL partition_maintenance(SCHEMA_NAME, history_log, 90, 24, 7); CALL partition_maintenance(SCHEMA_NAME, history_str, 90, 24, 7); CALL partition_maintenance(SCHEMA_NAME, history_text, 90, 24, 7); CALL partition_maintenance(SCHEMA_NAME, history_uint, 90, 24, 7); CALL partition_maintenance(SCHEMA_NAME, trends, 730, 24, 7); CALL partition_maintenance(SCHEMA_NAME, trends_uint, 730, 24, 7);
END$$
DELIMITER ; 语法格式 说明
CALL partition_maintenance(, , , , )
例 CALL partition_maintenance(SCHEMA_NAME, history, 90, 24, 7);
90: 意思是对history表未来保留90天分区的数据
24: 意思是 对history表 每24小时(1天)建立一个分区
7: 意思 是对history表每 次建立7个分区如果每天执行存储话比如今天3月23号第一次执行存储过程会创建3月23号到3月29号 7个分区明天3月24号创建3月24号到3月30号 7个分区但是因为24到29号的分区3月23号执行存储过程时已经建立就只会创建3月30号的一个分区。以后每天依此类推
另外因为我们zabbix已经有历史数据了第一次执行存储时会把所有的历史数据全部放入第一个3月23号的分区中
四、执行分表并写入日志
nohup /usr/bin/mysql -h127.0.0.1 -u zabbix -pZabbix123 -D zabbix -e CALL partition_maintenance_all(zabbix); /data/mysql/partition.log 21
mysql -uroot -p
use zabbix
show create table history; 如果显示这样则为分表正常
五、设定每日维护分区排程
#每天凌晨1点执行存储过程新建分区和删除历史分区
crontab -e
0 1 * * * /usr/bin/mysql -h127.0.0.1 -u zabbix -pZabbix123 -D zabbix -e CALL partition_maintenance_all(zabbix); 1/data/mysql/partition_job.log 2/data/mysql/partition_job.bad
六、启用zabbix服务
# 避免修改分区表时数据还有写入
systemctl start zabbix
七、 更改内部管家服务设定
#历史记录和趋势两个选项下的“开启内部管理服务”功能需要关闭 完成
