Hello,
I have problems with the housekeeper and growth of the database, which is no longer how to fix it properly.
My configuration is:
I'm using (learning) zabbix, for less than a year, and I think housekeeper never worked properly, which has increased the DB.
I think it always failed, until I realized that creating an index arranged "CREATE INDEX ON housekeeper_tablename housekeeper (tablename ASC);", But now the DB (tables/records) are too big for my "server" support data deletion.
Now (after creating the index) to run housekeeper fails because the server ends up running out of RAM
The query that produces this is: "select housekeeperid, tablename, field, value from tablename order by housekeeper"
Leaving the server:
No how to fix this .. DB keeps growing and growing, but I have no server that can run with the current configuration housekeeper.
Perform "Partitioning Tables" I'm not sure if it is useful at this stage (I have every item with different values of history and trends)
Delete records by hand, is like that gives me confidence for not understanding very well zabbix tables.
If I can help and guide me on the best solution will be very grateful (then just keep reading!)
Thanks for getting here.
I have problems with the housekeeper and growth of the database, which is no longer how to fix it properly.
My configuration is:
Code:
The Zabbix 1.8.7 running on SLES 11 SP1 with kernel 2.6.32.12-0.7-xen (in a virtual xen) Dom0 : CPU CPU Q8400 (Quad core), RAM 3GB DomU : 2GB RAM Number of hosts (monitored/not monitored/templates) 352 269 / 3 / 80 Number of items (monitored/disabled/not supported) 18546 8609 / 9624 / 313 Number of triggers (enabled/disabled)[problem/unknown/ok] 3924 2338 / 1586 [143 / 733 / 1462] Required server performance, new values per second 54.09 - housekeeper.ibd - 3,1GB history.ibd - 41G history_uint.ibd - 17G trends.ibd - 965M
I'm using (learning) zabbix, for less than a year, and I think housekeeper never worked properly, which has increased the DB.
I think it always failed, until I realized that creating an index arranged "CREATE INDEX ON housekeeper_tablename housekeeper (tablename ASC);", But now the DB (tables/records) are too big for my "server" support data deletion.
Now (after creating the index) to run housekeeper fails because the server ends up running out of RAM
The query that produces this is: "select housekeeperid, tablename, field, value from tablename order by housekeeper"
Leaving the server:
Code:
free -m
total used free shared buffers cached
Mem: 2012 1937 75 0 0 43
-/+ buffers/cache: 1892 120
Swap: 2047 2042 4
No how to fix this .. DB keeps growing and growing, but I have no server that can run with the current configuration housekeeper.
Perform "Partitioning Tables" I'm not sure if it is useful at this stage (I have every item with different values of history and trends)
Delete records by hand, is like that gives me confidence for not understanding very well zabbix tables.
If I can help and guide me on the best solution will be very grateful (then just keep reading!)
Thanks for getting here.