Ad Widget

Collapse

Changes to History Retention Settings Not Taking Effect

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • tim.mooney
    Senior Member
    • Dec 2012
    • 1427

    #16
    Originally posted by prchalsefira
    Housekeeper was set to run every hour and ran for approximately 50 hours. I understand that this probably caused the database to grow.
    Yeah, it probably won't ever "catch up" if it takes 50 hours to complete one run. Your updated config deleted 47.6 million history/trends records, but if I do my math correctly it took 52 hours to complete. Deleting 47 million records every two days, you probably are making progress, but it's pretty slow.

    Just out of curiosity, how many records are in your history and history_uint tables?

    You have kind of a strange install. You have a large # of hosts and items, but your NVPS isn't even 1/10th of what I was expecting for that many items. Do you have thousands of hosts that are no longer monitored, but haven't been deleted?

    Comment

    • prchalsefira
      Junior Member
      • Jan 2023
      • 5

      #17
      I created new history_* tables and copied only data for the last 30 days. Housekeeper now runs for 90 - 200 seconds and everything looks good. I'll continue to watch if the database doesn't get too big.

      Thank you all for the advice. I consider my problem solved.​

      Comment


      • greentaco
        greentaco commented
        Editing a comment
        Would you by chance by able to share exactly how you achieved the copy of only 30 days to the new table?
    Working...