zabbix db partition

reko_3

在做zabbix的性能优化时，有时候在db的数据量比较大的时候，需要对表进行partition操作，这样可以在数据查询减少用时。并且由于使用了partition，我们可以自己实现历史数据的删除操作，这样就可以禁用zabbix的housekeeping功能。


简单的说下再2.0.x版本的zabbix中进行partition的操作：
1.备份数据，如果使用proxy的结构的话，调整ProxyOfflineBuffer,加大数据在offline情况的缓存时间，这样在partition调整完后数据会自动补充。
　　确定需要partition的表，并更改表结构（使用clock进行parttition，partition key必须是primarykey的一部分），涉及的表主要是存储历史相关数据的表：history,history_uint,history_text,history_log,history_str
　　表结构更改：

ALTER TABLE `history_log` DROP PRIMARY KEY, ADD PRIMARY KEY (`itemid`,`id`,`clock`);
ALTER TABLE `history_log` DROP KEY `history_log_2`;
ALTER TABLE `history_text` DROP PRIMARY KEY, ADD PRIMARY KEY (`itemid`,`id`,`clock`);
ALTER TABLE `history_text` DROP KEY `history_text_2`;　　剩下的history_str,history,history_uint 3个表不需要做更改。

2.按clock进行分区
　　例子：
ALTER TABLE `history_uint` PARTITION BY RANGE( clock ) (
PARTITION p20140101 VALUES LESS THAN (UNIX_TIMESTAMP("2014-01-02 00:00:00")),
PARTITION p20140102 VALUES LESS THAN (UNIX_TIMESTAMP("2014-01-03 00:00:00")),
PARTITION p20140103 VALUES LESS THAN (UNIX_TIMESTAMP("2014-01-04 00:00:00")),
PARTITION p20140104 VALUES LESS THAN (UNIX_TIMESTAMP("2014-01-05 00:00:00")),
PARTITION p20140105 VALUES LESS THAN (UNIX_TIMESTAMP("2014-01-06 00:00:00")),
PARTITION p20140106 VALUES LESS THAN (UNIX_TIMESTAMP("2014-01-07 00:00:00"))
);把需要分区的表都进行相同的操作。
3.设置存储规则，并使用cronjob来实现自动partition操作
mysql -u xxx -pxxx xxx < ./partition.sql其中partition.sql的内容如下：
DELIMITER //
DROP PROCEDURE IF EXISTS `zabbix_server`.`create_zabbix_partitions` //
CREATE PROCEDURE `zabbix_server`.`create_zabbix_partitions` ()
BEGIN
CALL zabbix_server.create_next_partitions("zabbix_server","history");
CALL zabbix_server.create_next_partitions("zabbix_server","history_log");
CALL zabbix_server.create_next_partitions("zabbix_server","history_str");
CALL zabbix_server.create_next_partitions("zabbix_server","history_text");
CALL zabbix_server.create_next_partitions("zabbix_server","history_uint");
CALL zabbix_server.drop_old_partitions("zabbix_server","history");
CALL zabbix_server.drop_old_partitions("zabbix_server","history_log");
CALL zabbix_server.drop_old_partitions("zabbix_server","history_str");
CALL zabbix_server.drop_old_partitions("zabbix_server","history_text");
CALL zabbix_server.drop_old_partitions("zabbix_server","history_uint");
END //
DROP PROCEDURE IF EXISTS `zabbix_server`.`create_next_partitions` //
CREATE PROCEDURE `zabbix_server`.`create_next_partitions` (SCHEMANAME varchar(64), TABLENAME varchar(64))
BEGIN
DECLARE NEXTCLOCK timestamp;
DECLARE PARTITIONNAME varchar(16);
DECLARE CLOCK int;
SET @totaldays = 7;
SET @i = 1;
createloop: LOOP
SET NEXTCLOCK = DATE_ADD(NOW(),INTERVAL @i DAY);
SET PARTITIONNAME = DATE_FORMAT( NEXTCLOCK, 'p%Y%m%d' );
SET CLOCK = UNIX_TIMESTAMP(DATE_FORMAT(DATE_ADD( NEXTCLOCK ,INTERVAL 1 DAY),'%Y-%m-%d 00:00:00'));
CALL zabbix_server.create_partition( SCHEMANAME, TABLENAME, PARTITIONNAME, CLOCK );
SET @i=@i+1;
IF @i > @totaldays THEN
LEAVE createloop;
END IF;
END LOOP;
END //
DROP PROCEDURE IF EXISTS `zabbix_server`.`drop_old_partitions` //
CREATE PROCEDURE `zabbix_server`.`drop_old_partitions` (SCHEMANAME varchar(64), TABLENAME varchar(64))
BEGIN
DECLARE OLDCLOCK timestamp;
DECLARE PARTITIONNAME varchar(16);
DECLARE CLOCK int;
SET @mindays = 30;
SET @maxdays = @mindays+4;
SET @i = @maxdays;
droploop: LOOP
SET OLDCLOCK = DATE_SUB(NOW(),INTERVAL @i DAY);
SET PARTITIONNAME = DATE_FORMAT( OLDCLOCK, 'p%Y%m%d' );
CALL zabbix_server.drop_partition( SCHEMANAME, TABLENAME, PARTITIONNAME );
SET @i=@i-1;
IF @i  UNIX_TIMESTAMP()-1800 and delay < 900   and hostid in (select hostid from hosts where status=0)   and status = 0 group by hostid ) a RIGHT JOIN (select hostid,count(*) as bb from items where delay < 900 and status = 0 and hostid in (select hostid from hosts where status=0) group by hostid) b  ON a.hostid=b.hostid)a,(select hostid,lower(host) as hostname from hosts where status=0)b, (select hostid,ip from interface where type='1')c where a.hostid=b.hostid and b.hostid=c.hostid  order by uppercent;