Mysql優(yōu)化之Zabbix分區(qū)優(yōu)化
使用zabbix最大的瓶頸在于數(shù)據(jù)庫,維護(hù)好zabbix的數(shù)據(jù)存儲(chǔ),告警,就能很好地應(yīng)用zabbix去構(gòu)建監(jiān)控系統(tǒng)。目前zabbix的數(shù)據(jù)主要存儲(chǔ)在history和trends的2個(gè)表中,隨著時(shí)間的推移,這兩個(gè)表變得非常大,性能會(huì)非常差,影響監(jiān)控的使用。對MySQL進(jìn)行調(diào)優(yōu),能夠極大的提升Zabbix的性能,本文采用對MySQL進(jìn)行分區(qū)的方法進(jìn)行調(diào)優(yōu)。
原理
對zabbix中的history和trends等表進(jìn)行分區(qū),按日期進(jìn)行分區(qū),每天一個(gè),共保留90天分區(qū)。
操作詳細(xì)步驟
操作影響: 可以在線操作,MySQL的讀寫變慢,Zabbix性能變慢,影響時(shí)間根據(jù)數(shù)據(jù)的小而變化,一般在2個(gè)小時(shí)左右。
第一步
登錄zabbix server的數(shù)據(jù)庫,統(tǒng)一MySQL的配置
cat > /etc/my.cnf<<EOF [mysqld] datadir=/data/mysql socket=/var/lib/mysql/mysql.sock default-storage-engine = innodb collation-server = utf8_general_ci init-connect = 'SET NAMES utf8' character-set-server = utf8 symbolic-links=0 max_connections=4096 innodb_buffer_pool_size=12G max_allowed_packet = 32M join_buffer_size=2M sort_buffer_size=2M query_cache_size = 64M query_cache_limit = 4M thread_concurrency = 8 table_open_cache=1024 innodb_flush_log_at_trx_commit = 0 long_query_time = 1 log-slow-queries =/data/mysql/mysql-slow.log [mysqld_safe] log-error=/var/log/mariadb/mariadb.log pid-file=/var/run/mariadb/mariadb.pid #[mysql] #socket=/data/mysql/mysql.sock # # include all files from the config directory # !includedir /etc/my.cnf.d EOF
注意:一定要修改innodb_buffer_pool_size=物理內(nèi)存的1/3
第二步
先確認(rèn)zabbix的版本,本操作zabbix的版本一定要大于3.2.0。小于3.2的版本不能安裝此操作,線上默認(rèn)是zabbix-3.2.6。
a、 導(dǎo)入存儲(chǔ)過程
#cat partition.sql DELIMITER $$ CREATE PROCEDURE `partition_create`(SCHEMANAMEvarchar(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 ANDpartition_description >= CLOCK; IF RETROWS = 0 THEN /* 1. Print a messageindicating that a partition was created. 2. Create the SQL to createthe partition. 3. Execute the SQL from #2. */ SELECT CONCAT( "partition_create(", SCHEMANAME, ",",TABLENAME, ",", PARTITIONNAME, ",", CLOCK, ")" )AS msg; SET @sql = CONCAT( 'ALTER TABLE ', SCHEMANAME, '.', TABLENAME, ' ADDPARTITION (PARTITION ', PARTITIONNAME, ' VALUES LESS THAN (', CLOCK, '));' ); PREPARE STMT FROM @sql; EXECUTE STMT; DEALLOCATE PREPARE STMT; END IF; END$$ DELIMITER ; DELIMITER $$ CREATE PROCEDURE `partition_drop`(SCHEMANAMEVARCHAR(64), TABLENAME VARCHAR(64), DELETE_BELOW_PARTITION_DATE BIGINT) BEGIN /* SCHEMANAME = The DB schema in which tomake changes TABLENAME = The table with partitions to potentially delete DELETE_BELOW_PARTITION_DATE = Delete any partitions with names that aredates 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 TOget rid of that character. */ DECLARE myCursor CURSOR FOR SELECT partition_name FROM information_schema.partitions WHERE table_schema = SCHEMANAME AND table_name = TABLENAME ANDCAST(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 allthe necessary partitions. 2. Run the SQL to drop thepartitions. 3. Print out the tablepartitions 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 beingdeleted, 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 CALLpartition_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(), INTERVALKEEP_DATA_DAYS DAY), '%Y%m%d0000'); CALL partition_drop(SCHEMA_NAME, TABLE_NAME, OLDER_THAN_PARTITION_DATE); END$$ DELIMITER ; DELIMITER $$ CREATE PROCEDURE `partition_verify`(SCHEMANAMEVARCHAR(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 ANDpartition_name IS NULL; /* * If partitions do not exist, go ahead and partition the table */ IFRETROWS = 1 THEN /* * Take the current date at 00:00:00 and add HOURLYINTERVAL to it. This is the timestamp below which we willstore values. * We begin partitioning based on the beginning of a day. This is because we don't want to generate arandom 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" whenall 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, 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); CALLpartition_maintenance(SCHEMA_NAME, 'history_uint', 90, 24, 14); CALL partition_maintenance(SCHEMA_NAME, 'trends', 730, 24, 14); CALL partition_maintenance(SCHEMA_NAME, 'trends_uint', 730, 24, 14); END$$ DELIMITER ;
上面內(nèi)容包含了創(chuàng)建分區(qū)的存儲(chǔ)過程,將上面內(nèi)容復(fù)制到partition.sql中,然后執(zhí)行如下:
mysql -uzabbix -pzabbix zabbix < partition.sql
b、 添加crontable,每天執(zhí)行01點(diǎn)01分執(zhí)行,如下:
crontab -l > crontab.txt cat >> crontab.txt <<EOF #zabbix partition_maintenance 01 01 * * * mysql -uzabbix -pzabbix zabbix -e"CALL partition_maintenance_all('zabbix')" &>/dev/null EOF cat crontab.txt |crontab
注意: mysql的zabbix用戶的密碼部分按照實(shí)際環(huán)境配置
c、首先執(zhí)行一次(由于首次執(zhí)行的時(shí)間較長,請使用nohup執(zhí)行),如下:
nohup mysql -uzabbix -pzabbix zabbix -e "CALLpartition_maintenance_all('zabbix')" &> /root/partition.log&
注意:觀察/root/partition.log的輸出
d、 查看結(jié)果
登錄mysql,查看history等表, 如下:
MariaDB [zabbix]> showcreate table history | history | CREATE TABLE `history` ( `itemid` bigint(20) unsigned NOT NULL, `clock`int(11) NOT NULL DEFAULT '0', `value`double(16,4) NOT NULL DEFAULT '0.0000', `ns`int(11) NOT NULL DEFAULT '0', KEY`history_1` (`itemid`,`clock`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 /*!50100 PARTITION BY RANGE (`clock`) (PARTITION p201708280000 VALUES LESS THAN(1503936000) ENGINE = InnoDB, PARTITION p201708290000 VALUES LESS THAN(1504022400) ENGINE = InnoDB, PARTITION p201708300000 VALUES LESS THAN(1504108800) ENGINE = InnoDB, PARTITION p201708310000 VALUES LESS THAN(1504195200) ENGINE = InnoDB, PARTITION p201709010000 VALUES LESS THAN(1504281600) ENGINE = InnoDB, PARTITION p201709020000 VALUES LESS THAN(1504368000) ENGINE = InnoDB, PARTITION p201709030000 VALUES LESS THAN(1504454400) ENGINE = InnoDB, PARTITION p201709040000 VALUES LESS THAN(1504540800) ENGINE = InnoDB, PARTITION p201709050000 VALUES LESS THAN(1504627200) ENGINE = InnoDB, PARTITION p201709060000 VALUES LESS THAN(1504713600) ENGINE = InnoDB, PARTITION p201709070000 VALUES LESS THAN(1504800000) ENGINE = InnoDB, PARTITION p201709080000 VALUES LESS THAN(1504886400) ENGINE = InnoDB, PARTITION p201709090000 VALUES LESS THAN(1504972800) ENGINE = InnoDB, PARTITION p201709100000 VALUES LESS THAN(1505059200) ENGINE = InnoDB, PARTITION p201709110000 VALUES LESS THAN(1505145600) ENGINE = InnoDB) */ |
發(fā)現(xiàn)了大量PARTITION字段,說明配置正確。注意觀察Mysql的Slow Query,一般到執(zhí)行操作的第二天,Slow Query幾乎就會(huì)有了,此時(shí)Zabbix的Dashboard響應(yīng)速度應(yīng)該非常流暢了。
- MySQL高級(jí)特性——數(shù)據(jù)表分區(qū)的概念及機(jī)制詳解
- MySql分表、分庫、分片和分區(qū)知識(shí)深入詳解
- MySql分表、分庫、分片和分區(qū)知識(shí)點(diǎn)介紹
- MySQL分表和分區(qū)的具體實(shí)現(xiàn)方法
- mysql通過Navicat分區(qū)實(shí)操講解
- MySQL分區(qū)表的正確使用方法
- MySQL分區(qū)字段列有必要再單獨(dú)建索引嗎?
- MySQL數(shù)據(jù)庫表分區(qū)注意事項(xiàng)大全【推薦】
- Mysql數(shù)據(jù)表分區(qū)技術(shù)PARTITION淺析
- MySQL數(shù)據(jù)表分區(qū)策略及優(yōu)缺點(diǎn)分析
相關(guān)文章
mysql下為數(shù)據(jù)庫設(shè)置交叉權(quán)限的方法
由于 SupeSite 需要調(diào)用 Discuz! 和 UCHome 的數(shù)據(jù),所以如果它們不安裝在同一個(gè)數(shù)據(jù)庫,SupeSite 的數(shù)據(jù)庫用戶必須要對 Discuz! 和 UCHome 的數(shù)據(jù)庫有讀取、修改、刪除等權(quán)限。2011-07-07MySQL實(shí)戰(zhàn)記錄之如何快速定位慢SQL
這可能是困然很多人的一個(gè)問題,MySQL通過慢查詢?nèi)罩径ㄎ荒切﹫?zhí)行效率較低的SQL語句,下面這篇文章主要給大家介紹了關(guān)于MySQL實(shí)戰(zhàn)記錄之如何快速定位慢SQL的相關(guān)資料,需要的朋友可以參考下2022-03-03MySQL定時(shí)執(zhí)行腳本(計(jì)劃任務(wù))命令實(shí)例
在mysql中我們可以直接進(jìn)行一些參數(shù)設(shè)置讓它成定時(shí)為我們執(zhí)行一些任務(wù)了,這個(gè)雖然可以使用windows或者linux中的計(jì)劃任務(wù)實(shí)現(xiàn),但是mysql本身也能完成2013-10-10數(shù)據(jù)庫實(shí)現(xiàn)行列轉(zhuǎn)換(mysql示例)
最近突然玩起了sql語句,想著想著便給自己出了一道題目:“行列轉(zhuǎn)換”。起初瞎折騰了不少時(shí)間也上網(wǎng)參考了一些博文,不過大多數(shù)是采用oracle數(shù)據(jù)庫當(dāng)中的一些便捷函數(shù)進(jìn)行處理,比如”pivot”。那么,在Mysql環(huán)境下如何處理?下面通過這篇文章我們來一起看看吧。2016-12-12MySQL 創(chuàng)建用戶、授權(quán)用戶、撤銷用戶權(quán)限、更改用戶密碼、刪除用戶(實(shí)用技巧)
這篇文章主要介紹了MySQL 創(chuàng)建用戶、授權(quán)用戶、撤銷用戶權(quán)限、更改用戶密碼、刪除用戶(實(shí)用技巧),需要的朋友可以參考下2017-03-03詳解MySQL數(shù)據(jù)備份之mysqldump使用方法
本篇文章主要介紹了MySQL數(shù)據(jù)備份,詳細(xì)的介紹了mysqldump的各種用法,具有一定的參考價(jià)值,有需要的可以了解一下。2016-11-11Mac環(huán)境mysql5.7.21 utf8編碼問題及解決方案
本篇教程給大家簡單介紹下Mac環(huán)境mysql5.7.21 utf8編碼問題及解決方案,非常不錯(cuò),具有參考借鑒價(jià)值,需要的朋友參考下吧2018-03-03