Ad Widget

Collapse

Help with Housekeeper Processes (100% busy for 3 hours every hour)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • kernbug
    Senior Member
    • Feb 2013
    • 330

    #16
    Originally posted by scuba
    At least its severity should be 'Information'
    Nope. If we look at the current load on the disk subsystem, then we are more likely to find problems with performance, at 100%(many hours) load on the housekeeper.
    Most performance problems are often caused by insufficient performance of the database (hardware and software settings) used.

    Comment

    • kloczek
      Senior Member
      • Jun 2006
      • 1771

      #17
      Originally posted by scuba
      If so , why it's listed in the problems list. At least its severity should be 'Information'
      Such alarm it is more like template issue (if it is with high severity).
      Problem may be if HK process will be running to long. It always means that something in zabbix stack needs to be changed.
      If for example HK spends to much time in history tables to delete oldest data it means that housekeeper process should be disabled after introduce partitioned history* tables and delete oldest data by dropping oldest history* tables partitions.
      Maintaining history*/trends* tables content without partitioning is OK in some small/POC zabbix stacks only.
      http://uk.linkedin.com/pub/tomasz-k%...zko/6/940/430/
      https://kloczek.wordpress.com/
      zapish - Zabbix API SHell binding https://github.com/kloczek/zapish
      My zabbix templates https://github.com/kloczek/zabbix-templates

      Comment

      • lpossamai
        Senior Member
        • Jun 2018
        • 119

        #18
        Originally posted by vso
        Which version do you use? Does upgrading to latest one help ?
        Zabbix Server 3.4. It's been running for less than a month and the DB size is already 4GB. Imagine in 2 years!!!

        Comment

        • kloczek
          Senior Member
          • Jun 2006
          • 1771

          #19
          If you will be using for example exactly the same history period (let's say 2 weeks) or raw monitoring data. With 3 years trends data those trends data may take 5-8% of whole database size.
          Problem is that probably you are still using OOTB templates which have on most of the items 90 days of history period so your database may reach still max in next two months ans if you will be not using partitioned history* tables you database still will be slowly growing even if ~number of monitoring points data will be ~const.

          Part of the proper zabbix administration is taking care of proper database backend maintenance which is part of the general DB support tasks .. and/or has nothing to do with zabbix per se.
          http://uk.linkedin.com/pub/tomasz-k%...zko/6/940/430/
          https://kloczek.wordpress.com/
          zapish - Zabbix API SHell binding https://github.com/kloczek/zapish
          My zabbix templates https://github.com/kloczek/zabbix-templates

          Comment

          • lahiruabeysinghe
            Junior Member
            • Apr 2023
            • 6

            #20
            Originally posted by scuba
            If so , why it's listed in the problems list. At least its severity should be 'Information'
            The trigger which relates to this Problem checks if the value is not just above 75%, but also if it averages that value over 30 mins. Housekeeping process running for 30 mins is the "Problem".

            Comment

            Working...