清理 zabbix 歷史資料, 縮減 mysql 空間
阿新 • • 發佈：2018-12-26
zabbix 由於歷史資料過大, 因此導致磁碟空間暴漲, 下面是結局方法步驟
1. 停止 ZABBIX SERER 操作
[[email protected] ~]# killall zabbix_server
[[email protected] ~]# lsof -i:100512. 停止 mysql 操作
[[email protected] dbdat]# mysqladmin -u root -p -h 127.0.0.1 shutdown3. 修改 my.cnf
新增 skip-new 引數, 目標可用縮減 innodb 磁碟空間
4. 重啟啟動 mysql
/apps/svr/mysql/bin/mysqld_safe --defaults-file=/apps/conf/mysql5.6/my.cnf --ledir=/apps/svr/mysql/bin --basedir=/apps/svr/mysql/ --datadir=/apps/dbdat/mysql5_data --user=apps & [[email protected] apps]# lsof -i:3306 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME mysqld 25527 apps 11u IPv4 29371110 0t0 TCP *:mysql (LISTEN)
5. 分析 history 表
mysql> desc history; +--------+---------------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +--------+---------------------+------+-----+---------+-------+ | itemid | bigint(20) unsigned | NO | MUL | NULL | | | clock | int(11) | NO | | 0 | | | value | double(16,4) | NO | | 0.0000 | | | ns | int(11) | NO | | 0 | | +--------+---------------------+------+-----+---------+-------+ 4 rows in set (0.00 sec) mysql> select max(itemid) from history; +-------------+ | max(itemid) | +-------------+ | 46582 | +-------------+ 1 row in set (0.00 sec) mysql> select * from history where itemid=46582 limit 1, 20; +--------+------------+--------+-----------+ | itemid | clock | value | ns | +--------+------------+--------+-----------+ | 46582 | 1396361332 | 0.0000 | 81875000 | | 46582 | 1396361362 | 0.0000 | 768297000 | | 46582 | 1396361392 | 0.0000 | 656787000 | | 46582 | 1396361422 | 0.0000 | 665169000 | | 46582 | 1396361452 | 0.0000 | 973570000 | | 46582 | 1396361482 | 0.0000 | 625619000 | | 46582 | 1396361512 | 0.0000 | 292743000 | | 46582 | 1396361543 | 0.0000 | 340000 | | 46582 | 1396361572 | 0.0000 | 15651000 | | 46582 | 1396361602 | 0.0000 | 153264000 | | 46582 | 1396361632 | 0.0000 | 79316000 | | 46582 | 1396361662 | 0.0000 | 308107000 | | 46582 | 1396361692 | 0.0000 | 237146000 | | 46582 | 1396361722 | 0.0000 | 108810000 | | 46582 | 1396361752 | 0.0000 | 419398000 | | 46582 | 1396361782 | 0.0000 | 284113000 | | 46582 | 1396361812 | 0.0000 | 254230000 | | 46582 | 1396361842 | 0.0000 | 145938000 | | 46582 | 1396361872 | 0.0000 | 403163000 | | 46582 | 1396361902 | 0.3300 | 193302000 | +--------+------------+--------+-----------+ 20 rows in set (0.01 sec)
6. 刪除兩週前資料方法
取得時間戳, 時間只保留至 2014 3 25 日
[[email protected] api]# date +%s -d "Mar 25, 2014 00:00:00"
1395676800刪除 history, history_unit 表方法
mysql> delete from history where clock < 1395676800;
Query OK, 8961912 rows affected (17 min 22.06 sec)
mysql> delete from history_uint where clock < 1395676800;
Query OK, 7789494 rows affected (21 min 38.02 sec)
嘗試對錶進行縮減發生故障
mysql> optimize table history_uint;
ERROR 1114 (HY000): The table '#sql-63b7_2d' is full
mysql> quit
Bye
[[email protected] mysql5_data]# df -h
檔案系統 容量 已用 可用 已用% 掛載點
/dev/vda1 20G 18G 1.3G 94% /
tmpfs 2.0G 0 2.0G 0% /dev/shm
故障原因, 當前 / 下磁碟空間不夠.
臨時刪除 swapfile
[[email protected] /]# swapoff -a
[[email protected] /]# rm -rf swapfile
[[email protected] /]# df -h
檔案系統 容量 已用 可用 已用% 掛載點
/dev/vda1 20G 15G 3.7G 81% /
tmpfs 2.0G 0 2.0G 0% /dev/shm原理說明, mysql 執行 optimize 過程中, 生成了臨時表見下面檔案, mysql 直接吧 history_unit 表複製成臨時表再重新改名, 實現空間縮減.
[[email protected] zabbix]# ls *63b7_2e* -lh
-rw-rw---- 1 apps apps 8.5K 04-02 12:04 #sql-63b7_2e.frm
-rw-rw---- 1 apps apps 1.1G 04-02 12:10 #sql-63b7_2e.ibd再次縮減
mysql> optimize table history_uint;
Query OK, 40496963 rows affected (20 min 0.04 sec)
Records: 40496963 Duplicates: 0 Warnings: 0
mysql> optimize table history;
Query OK, 45998084 rows affected (21 min 54.99 sec)
Records: 45998084 Duplicates: 0 Warnings: 0
7. 縮減前後文件大小比較
縮減前
[[email protected] mysql5_data]# find -size +50M -exec ls -lh {} \;
-rw-rw---- 1 apps apps 80M 04-02 10:29 ./zabbix/events.ibd
-rw-rw---- 1 apps apps 5.1G 04-02 11:44 ./zabbix/history.ibd
-rw-rw---- 1 apps apps 152M 04-02 10:29 ./zabbix/trends.ibd
-rw-rw---- 1 apps apps 4.3G 04-02 11:47 ./zabbix/history_uint.ibd
-rw-rw---- 1 apps apps 328M 04-02 10:29 ./zabbix/trends_uint.ibd
-rw-rw---- 1 apps apps 1.1G 04-02 11:47 ./ibdata1縮減後
[[email protected] mysql5_data]# find -size +50M -exec ls -lh {} \;
-rw-rw---- 1 apps apps 80M 04-02 10:29 ./zabbix/events.ibd
-rw-rw---- 1 apps apps 3.6G 04-02 13:30 ./zabbix/history.ibd
-rw-rw---- 1 apps apps 152M 04-02 10:29 ./zabbix/trends.ibd
-rw-rw---- 1 apps apps 3.2G 04-02 12:24 ./zabbix/history_uint.ibd
-rw-rw---- 1 apps apps 328M 04-02 10:29 ./zabbix/trends_uint.ibd
-rw-rw---- 1 apps apps 1.1G 04-02 13:30 ./ibdata18. 重啟啟動 zabbix, php, nginx, mysql
新問題出現:
當前 zabbix 進行初始化, 會對 mysql 進行大量資料 r/w 操作
因此可能會發生下面警報, 經過 5 分鐘後初始化, 下面報警會自動消除, 不用擔心.
Disk I/O is overloaded on gd02-qa-plxt2-nodomain-web-96.vclound.com
Zabbix history syncer processes more than 75% busy
Zabbix timer processes more than 75% busy