zabbix表分區(適用于zabbix2.0.x,zabbix2.2.x和zabbix2.4.x)

本文主要介紹了zabbix進行數據庫表分區的方法:

        在系統監控中,zabbix已經代替了nagios+cacti,zabbix以其良好的圖形展示和高度自定義贏得了很多運維人員的喜愛。但是由于在工作中,zabbix跑的時間過長(我們公司跑了將近3年),web頁面經??D,監控數據有時很難插入數據庫,且數據庫隊列經常性卡死,經過查看,發現mysql的數據量高達83G,急需瘦身,于是有了此文。

步驟:

  1. 修改表結構:

    use zabbix;

    Alter table history_text drop primary key, add index (id), drop index history_text_2, add index history_text_2 (itemid, id);
    Alter table history_log drop primary key, add index (id), drop index history_log_2, add index history_log_2 (itemid, id)

  2. 創建四大存儲過程:

    1. 分區創建的存儲過程:

      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 ;

    2. 分區刪除的存儲過程:

      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 ;

    3. 分區維護的存儲過程:

      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=@__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 ;

    4. 分區校驗的存儲過程:

      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 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 ;

  3. 存儲過程的使用:

    存儲過程如果單獨使用:CALL partition_maintenance(zabbix, 'history_uint', 31, 24, 14);

    解釋:history_uint表最多保存31天的數據,每隔24小時生成一個分區,這次一共生成14個分區

    可以使用一個存儲過程來實現7張表的分區:

    DELIMITER $$
    CREATE PROCEDURE `partition_maintenance_all`(SCHEMA_NAME VARCHAR(32))
    BEGIN
           CALL partition_maintenance(SCHEMA_NAME, 'history', 31, 24, 14);
           CALL partition_maintenance(SCHEMA_NAME, 'history_log', 31, 24, 14);
           CALL partition_maintenance(SCHEMA_NAME, 'history_str', 31, 24, 14);
           CALL partition_maintenance(SCHEMA_NAME, 'history_text', 31, 24, 14);
           CALL partition_maintenance(SCHEMA_NAME, 'history_uint', 31, 24, 14);
           CALL partition_maintenance(SCHEMA_NAME, 'trends', 180, 24, 14);
           CALL partition_maintenance(SCHEMA_NAME, 'trends_uint', 180, 24, 14);
    END$$
    DELIMITER ;

  4. 定時任務,使工作自動化:

    01 01 * * * /opt/software/mysql/bin/mysql -uzabbix -pzabbix zabbix -e "CALL partition_maintenance_all('zabbix');"

注:建議表分區任務和備份任務一起進行

特別感謝:51的”檸檬“請務必保持出處 附原文鏈接:http://xianglinhu.blog.51cto.com/5787032/1700981

               zabbix社區:https://www.zabbix.org/wiki/Docs/howto/mysql_partition

原創文章,作者:graysky,如若轉載,請注明出處:http://www.www58058.com/9009

(0)
grayskygraysky
上一篇 2015-10-27
下一篇 2015-10-27

相關推薦

  • Mysql 多表聯合查詢效率分析及優化

    1. 多表連接類型 1. 笛卡爾積(交叉連接) 在MySQL中可以為CROSS JOIN或者省略CROSS即JOIN,或者使用','  如:  SELECT * FROM table1 CROSS JOIN table2  &nb…

    Linux干貨 2015-04-13
  • rsyslog+mysql+loganalyzer配置

    rsyslog+mysql+loganalyzer 自定義日志存儲的信道(facility)和存儲位置,讓rsyslog作為服務端記錄rsyslog客戶端的日志信息 環境介紹 以centos 7.2為系統環境 內部已裝有mariadb、 一、準備工作 1、 安裝rsyslog連接至mysql server的驅動模塊;   # y…

    Linux干貨 2016-10-21
  • 馬哥教育網絡班25期-第3周作業

    1、列出當前系統上所有已經登錄的用戶的用戶名,注意:同一個用戶登錄多次,則只顯示一次即可。 [root@localhost ~]# who root     tty1         2016-12-…

    Linux干貨 2016-12-19
  • 搭建yum倉庫的FTP服務器

    搭建centos7ftp服務

    2017-12-02
  • 第一篇博客

    我的第一篇博客以及接下來的每一篇都要獻給linux運維了。第一次接觸linux是在大三的時候,當時并沒有想到以后還會和linux邂逅并以此謀生。 首先就從最基礎的linux分區與掛載點開始了解介紹,我們熟悉的Windows系統下的分區都分配有盤符,像c盤,d盤之類的,用來存放各種軟件和文件。而linux也有自己的分區,并將分區掛載到不同的掛載點上,掛載是指將…

    2017-07-16
  • ansible 入門與進階

    ansible 入門與進階 Configuration、Command and Control 是什么 ? SSH-based configuration management, deployment, and task execution system 運維工具的分類: agent:基于專用的agent程序完成管理功能,puppet, func, zabb…

    2016-11-09

評論列表(2條)

  • stanley
    stanley 2015-10-27 23:24

    db研究的好熟練,贊
    格式上如果能稍做調整,一定極為吸睛

  • 逗逗
    逗逗 2015-12-20 21:35

    大神,能提高點 zabbix 監控模版么,嘿嘿。

欧美性久久久久