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 23:21
下一篇 2015-10-27 23:25

相關推薦

  • bash腳本編程之流程控制if、for、while、until簡介

    概述     之前介紹了一些bash腳本編程的變量、運算、條件測試的一些基礎內容,了解了腳本實際上就是一些語句加上一些流程控制組合起來,實現某種功能的可執行文件。我們知道,條件測試的目的,實際就是為了實現一種流程的控制,那么本篇就簡單介紹一下bash里面常見的流程控制語句,包括選擇、循環等內容,具體包括以下幾個部分: …

    Linux干貨 2016-08-18
  • bash工作特性之命令執行狀態返回值和命令行展開的講解和實例

    命令執行狀態返回值 在Linux bash中可以用命令執行狀態返回值來判斷命令是否運行成功,而不需去關心命令返回的結果是多少。 bash通過狀態返回值來得到輸出結果; 成功:返回值 0 [root@localhost tmp]# ls aaa [root@localhost tmp]# mkdir $(date +%H-%m-%S) [root@localh…

    Linux干貨 2018-03-01
  • N25 The first week –Yorick

    1.計算機的組成及功能 ENIARC:馮諾依曼體系 1.1.運算器(所屬CPU)     進行計算 1.2.控制器(所屬CPU)     控制部件之間的協調,包括尋址操作     輔助性存儲(加速與提升CPU性能)     寄存器(鎖存數據)     緩存(緩…

    Linux干貨 2016-12-04
  • find命令

          find:實時查找工具,根據我們指定的內容或者條件在系統上進行實時查找,比locate在實際場景中用的多得多的多      具體用法:find   查找路徑      查找條件         &n…

    Linux干貨 2017-04-10
  • shell腳本基礎

    程序是由指令加數據組成 編程風格分為過程式和對象時 過程式:以指令為中心,數據服務于指令,適合小型程序 對象式:以數據為中心,指令服務于數據,社和大型程序 高級語言的執行方式分為編譯型和解釋型 編譯型:先將高級語言通過編譯器編譯成二進制代碼再執行 解釋型:程序編寫完成后不轉換成二進制代碼,在使用時才通過解釋器解釋運行,不生成二進制程序 shell就是一種解釋…

    Linux干貨 2016-08-18
  • Centos6.5利用RubyGems的fpm制作zabbix_agent的rpm包,并使用ansible批量部署

    一、 搭建rpm包制作環境 安裝gcc [root@lvs1 ~]# yum install gcc 安裝make [root@lvs1 ~]# yum install make 安裝ruby源(ruby版本必須要在1.9.3以上,centos自帶的是1.8的版本,需要自己編譯安…

    Linux干貨 2016-08-20

評論列表(2條)

  • stanley
    stanley 2015-10-27 23:24

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

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

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

欧美性久久久久