zabiix表格突然没有数据了_zabbix无法查询数据库 Table has no partition for value

当Zabbix显示数据为空时,问题可能出在MySQL历史表分区上。错误[1526] Table has no partition for value表明插入的数据超出了现有分区范围。解决方案包括检查并重建历史表分区,以及创建存储过程自动化分区维护,以防止未来再次出现类似问题。
摘要由CSDN通过智能技术生成

通过grafana查看zabbix的数据发现数据为空

重启zabbix-server以及在zabbix-server上获取agent的key都是正常的。

通过zabbix-server的日志发现

1006183:20201027:000001.680 [Z3005] query failed: [1526] Table has no partition for value 1603724401 [insert into history (itemid,clock,ns,value) values (581161,1603724401,679475011,0.003825);

有大量的此类报错,将此类sql 在mysql中执行报错,报错大概是说没有找到分区

mysql报错为

Aborted connection 24 to db: 'zabbix' user: 'zabbix' host: '127.0.0.1' (Got an error reading communication packets)

通过上诉报错基本可以确认导致报错的原因是zabbix-server插入mysql数据 找不表的对应分区

最初搭建zabbix的时候,担心单表过大,所有对历史表做了分区的操作,后因为压力原因将zabbix进行了迁移,迁移前将数据清空了,由此怀疑之前清空数据的时候把之前的表的分区也清空了,导致现在查询 插入都报错。

解决方案:

先关闭zabbix-server

1、查看关于历史(history)表的建表语句;当时对所有的历史表进行了分区,因此需要查询每个表

SHOW CREATE TABLE 分过区的表名;

例:

>use zabbix;

>SHOW CREATE TABLE history;

| history_bak | CREATE TABLE `history_bak` (

`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`),

KEY `clock` (`clock`)

) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin

/*!50100 PARTITION BY RANGE (`clock`)

(PARTITION p202009150000 VALUES LESS THAN (1600182000) ENGINE = InnoDB,

PARTITION p202009160000 VALUES LESS THAN (1600268400) ENGINE = InnoDB,

PARTITION p202009170000 VALUES LESS THAN (1600354800) ENGINE = InnoDB,

PARTITION p202009180000 VALUES LESS THAN (1600441200) ENGINE = InnoDB,

PARTITION p202009190000 VALUES LESS THAN (1600527600) ENGINE = InnoDB,

PARTITION p202009200000 VALUES LESS THAN (1600614000) ENGINE = InnoDB,

PARTITION p202009210000 VALUES LESS THAN (1600700400) ENGINE = InnoDB,

PARTITION p202009220000 VALUES LESS THAN (1600786800) ENGINE = InnoDB,

PARTITION p202009230000 VALUES LESS THAN (1600873200) ENGINE = InnoDB,

PARTITION p202009240000 VALUES LESS THAN (1600959600) ENGINE = InnoDB,

PARTITION p202009250000 VALUES LESS THAN (1601046000) ENGINE = InnoDB,

PARTITION p202009260000 VALUES LESS THAN (1601132400) ENGINE = InnoDB,

PARTITION p202009270000 VALUES LESS THAN (1601218800) ENGINE = InnoDB,

PARTITION p202009280000 VALUES LESS THAN (1601305200) ENGINE = InnoDB,

PARTITION p202009290000 VALUES LESS THAN (1601391600) ENGINE = InnoDB,

PARTITION p202009300000 VALUES LESS THAN (1601478000) ENGINE = InnoDB,

PARTITION p202010010000 VALUES LESS THAN (1601564400) ENGINE = InnoDB,

PARTITION p202010020000 VALUES LESS THAN (1601650800) ENGINE = InnoDB,

PARTITION p202010030000 VALUES LESS THAN (1601737200) ENGINE = InnoDB,

PARTITION p202010040000 VALUES LESS THAN (1601823600) ENGINE = InnoDB,

PARTITION p202010050000 VALUES LESS THAN (1601910000) ENGINE = InnoDB,

PARTITION p202010060000 VALUES LESS THAN (1601996400) ENGINE = InnoDB,

PARTITION p202010070000 VALUES LESS THAN (1602082800) ENGINE = InnoDB,

PARTITION p202010080000 VALUES LESS THAN (1602169200) ENGINE = InnoDB,

PARTITION p202010090000 VALUES LESS THAN (1602255600) ENGINE = InnoDB,

PARTITION p202010100000 VALUES LESS THAN (1602342000) ENGINE = InnoDB,

PARTITION p202010110000 VALUES LESS THAN (1602428400) ENGINE = InnoDB,

PARTITION p202010120000 VALUES LESS THAN (1602514800) ENGINE = InnoDB,

PARTITION p202010130000 VALUES LESS THAN (1602601200) ENGINE = InnoDB,

PARTITION p202010140000 VALUES LESS THAN (1602687600) ENGINE = InnoDB,

PARTITION p202010150000 VALUES LESS THAN (1602774000) ENGINE = InnoDB,

PARTITION p202010160000 VALUES LESS THAN (1602860400) ENGINE = InnoDB,

PARTITION p202010170000 VALUES LESS THAN (1602946800) ENGINE = InnoDB,

PARTITION p202010180000 VALUES LESS THAN (1603033200) ENGINE = InnoDB,

PARTITION p202010190000 VALUES LESS THAN (1603119600) ENGINE = InnoDB,

PARTITION p202010200000 VALUES LESS THAN (1603206000) ENGINE = InnoDB,

PARTITION p202010210000 VALUES LESS THAN (1603292400) ENGINE = InnoDB,

PARTITION p202010220000 VALUES LESS THAN (1603378800) ENGINE = InnoDB,

PARTITION p202010230000 VALUES LESS THAN (1603465200) ENGINE = InnoDB,

PARTITION p202010240000 VALUES LESS THAN (1603551600) ENGINE = InnoDB,

PARTITION p202010250000 VALUES LESS THAN (1603638000) ENGINE = InnoDB,

PARTITION p202010260000 VALUES LESS THAN (1603724400) ENGINE = InnoDB) */ |

+-------------+---------------------------------------------------------------

其中建表语句为

CREATE TABLE `history_bak` (

`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`),

KEY `clock` (`clock`)

) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin;

2、将原表重命令,已备创建表失败及时查看使用(每个history表都要执行)

alter table 表名 rename to 修改后的表名;

例:alter table history rename to history_bak;

3、执行创表语句(每个history表都要执行)

执行1、获取的sql语句

例:

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`),

KEY `clock` (`clock`)

) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin;

4、打开zabbix-server 检查数据可以正常读取

以上步骤只是可以暂时让zabbix可用,但一段时候后同样的现象还是会出现

彻底解决

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 ;

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 ;

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 ;

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 ;

2、重新执行表分区命令

做成一个统一的表

DELIMITER $$

CREATE PROCEDURE `partition_maintenance_all`(SCHEMA_NAME VARCHAR(32))

BEGIN

CALL partition_maintenance(SCHEMA_NAME, 'history', 28, 24, 14);

CALL partition_maintenance(SCHEMA_NAME, 'history_log', 28, 24, 14);

CALL partition_maintenance(SCHEMA_NAME, 'history_str', 28, 24, 14);

CALL partition_maintenance(SCHEMA_NAME, 'history_text', 28, 24, 14);

CALL partition_maintenance(SCHEMA_NAME, 'history_uint', 28, 24, 14);

CALL partition_maintenance(SCHEMA_NAME, 'trends', 730, 24, 14);

CALL partition_maintenance(SCHEMA_NAME, 'trends_uint', 730, 24, 14);

END$$

DELIMITER ;

mysql> CALL partition_maintenance_all('zabbix');

3、将表分区命令加入到crontab

crontab -l|tail -1

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

  • 0
    点赞
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值