Mysql優(yōu)化之Zabbix分區(qū)優(yōu)化
使用zabbix最大的瓶頸在于數(shù)據(jù)庫(kù),維護(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)控的使用。對(duì)MySQL進(jìn)行調(diào)優(yōu),能夠極大的提升Zabbix的性能,本文采用對(duì)MySQL進(jìn)行分區(qū)的方法進(jìn)行調(diào)優(yōu)。
原理
對(duì)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ù)庫(kù),統(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í)間較長(zhǎng),請(qǐng)使用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分表、分庫(kù)、分片和分區(qū)知識(shí)深入詳解
- MySql分表、分庫(kù)、分片和分區(qū)知識(shí)點(diǎn)介紹
- MySQL分表和分區(qū)的具體實(shí)現(xiàn)方法
- mysql通過Navicat分區(qū)實(shí)操講解
- MySQL分區(qū)表的正確使用方法
- MySQL分區(qū)字段列有必要再單獨(dú)建索引嗎?
- MySQL數(shù)據(jù)庫(kù)表分區(qū)注意事項(xiàng)大全【推薦】
- Mysql數(shù)據(jù)表分區(qū)技術(shù)PARTITION淺析
- MySQL數(shù)據(jù)表分區(qū)策略及優(yōu)缺點(diǎn)分析
相關(guān)文章
淺談MySql整型索引和字符串索引失效或隱式轉(zhuǎn)換問題
本文主要介紹了MySql整型索引和字符串索引失效或隱式轉(zhuǎn)換問題,文中通過示例代碼介紹的非常詳細(xì),具有一定的參考價(jià)值,感興趣的小伙伴們可以參考一下2021-11-11
mysql 5.7.17 免安裝版配置方法圖文教程(windows10)
這篇文章主要為大家詳細(xì)介紹了windows10下mysql 5.7.17 免安裝版配置方法圖文教程,具有一定的參考價(jià)值,感興趣的小伙伴們可以參考一下2017-01-01
CentOS7安裝MySQL8的超級(jí)詳細(xì)教程(無坑!)
我們?cè)贚inux系統(tǒng)中,如果要使用關(guān)系型數(shù)據(jù)庫(kù)的話,基本都是用的mysql,這篇文章主要給大家介紹了關(guān)于CentOS7安裝MySQL8的相關(guān)資料,文中通過實(shí)例代碼介紹的非常詳細(xì),需要的朋友可以參考下2022-06-06
Mysql一對(duì)多輕松實(shí)現(xiàn)追蹤歷史首條記錄
本文介紹了在數(shù)據(jù)庫(kù)中處理一對(duì)多關(guān)系時(shí),如何使用JOIN和WHERE子句來找到每個(gè)主表記錄對(duì)應(yīng)的子表中特定記錄(例如時(shí)間最早的記錄),通過將B表與自身進(jìn)行比較并使用MIN()函數(shù),可以精確匹配到所需記錄2024-12-12
Linux mysql命令安裝允許遠(yuǎn)程連接的安裝設(shè)置方法
對(duì)大家推薦很好使用的Linux mysql系統(tǒng),像讓大家對(duì)Linux mysql系統(tǒng)有所了解,然后對(duì)Linux mysql系統(tǒng)全面講解介紹,希望對(duì)大家有用今天特意配置了mysql apache php ,雖然網(wǎng)上很多這方面的例子,但是很多是作者再回憶寫的,所以難免有筆誤的地方。2010-08-08
mysql多個(gè)TimeStamp設(shè)置的方法解讀
timestamp設(shè)置默認(rèn)值是Default CURRENT_TIMESTAMP;timestamp設(shè)置隨著表變化而自動(dòng)更新是ON UPDATE CURRENT_TIMESTAMP;接下來為您詳細(xì)介紹2012-11-11
MYSQL查看時(shí)區(qū)并設(shè)置時(shí)區(qū)的實(shí)現(xiàn)示例
本文主要介紹了MYSQL查看時(shí)區(qū)并設(shè)置時(shí)區(qū)的實(shí)現(xiàn)示例,包括查看全局和會(huì)話時(shí)區(qū)設(shè)置,設(shè)置全局和會(huì)話時(shí)區(qū)為東八區(qū),具有一定的參考價(jià)值,感興趣的可以了解一下2025-03-03
sql server自動(dòng)編號(hào)的三種方法
自增列是最簡(jiǎn)單和常見的方法,適用于大多數(shù)情況,本文介紹了SQL Server中三種常見的自動(dòng)編號(hào)方法:自增列、序列和觸發(fā)器,具有一定的參考價(jià)值,感興趣的可以了解一下2023-10-10
MySQL 5.7升級(jí)8.0后出現(xiàn)排序規(guī)則問題的解決方案匯總
MySQL 5.7.34 升級(jí)到 8.0.32 后部分查詢語句報(bào)錯(cuò)如下,ERROR 1267 (HY000),比較操作中使用不同的字符集或排序規(guī)則通常會(huì)觸發(fā)此問題,所以本文給大家介紹了MySQL 5.7升級(jí)8.0后出現(xiàn)排序規(guī)則問題的解決方案匯總,需要的朋友可以參考下2024-06-06

