Housekeeper clean-up in 1.8.15 uses wrong timestamps?

[Mojah]

Hi,

We have a zabbix 1.8.15 setup running and are planning to migrate to 2.x, but first we have to clean our database a bit to make the migration less painful. While checking the database, we found the following anomaly.

An item is configured as such:
Keep history (in days): 2
Keep trends (in days): 7

Here's the DELETE statement that Zabbix Housekeeper runs:

mysql > delete from history_uint where itemid=54612 and clock<1357283293

That clock timestamp converts to 2013-01-04, 08:08:13. The current date is 2013-01-09, 11:03:00.
That's a 5 day difference for the Housekeeper query, where it should actually delete all the data that is older than 2 days, not 5?

What causes this? Am I missing an obvious time-conversion here? Or is there possible a problem in the housekeeper cleanups?

We have the following config in our Zabbix Server:

# If set to 0 then no limit is used at all.
MaxHousekeeperDelete=0
DisableHousekeeping=0

Regards,
Mattias

[Mojah]

To answer my own post, this is further described here:
- Forum post: https://www.zabbix.com/forum/showthr...t=24983&page=2
- Bugreport: https://support.zabbix.com/browse/ZBX-5887

It's "intended behaviour", but this causes more data to be kept in the database because it's only removed in smaller chunks. Hence, lowering the "Keep history for x days" value for an item drastically will only yield results over a longer period of time.