Ad Widget

Collapse

zabbix history syncer processes more than 75 busy

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • dumi
    Junior Member
    • Dec 2014
    • 7

    #1

    zabbix history syncer processes more than 75 busy

    Hello,

    From time to time on my zabbix server i receive the following error: "zabbix history syncer processes more than 75 busy". When this happens the server show all the host monitored by agent down, the interface its slow and eventually crash. Then i need to reboot the operating system to bring the server back online.

    Zabbix ver.: 2.0.12
    DB: mysql
    OS: centos 6.5

    Some printscreen and graphs for you to understand better the problem with my zabbix server:

    https://drive.google.com/open?id=0B_NFTkthQa4xVGVqQUx1c2ExWnM&authuser=0





    And of course zabbix_server.conf:

    Code:
    # This is a configuration file for Zabbix Server process
    # To get more information about Zabbix,
    # visit http://www.zabbix.com
    
    ############ GENERAL PARAMETERS #################
    
    ### Option: NodeID
    #       Unique NodeID in distributed setup.
    #       0 - standalone server
    #
    # Mandatory: no
    # Range: 0-999
    # Default:
    # NodeID=0
    
    ### Option: ListenPort
    #       Listen port for trapper.
    #
    # Mandatory: no
    # Range: 1024-32767
    # Default:
    # ListenPort=10051
    
    ### Option: SourceIP
    #       Source IP address for outgoing connections.
    #
    # Mandatory: no
    # Default:
    # SourceIP=
    
    ### Option: LogFile
    #       Name of log file.
    #       If not set, syslog is used.
    #
    # Mandatory: no
    # Default:
    # LogFile=
    
    LogFile=/var/log/zabbix/zabbix_server.log
    
    ### Option: LogFileSize
    #       Maximum size of log file in MB.
    #       0 - disable automatic log rotation.
    #
    # Mandatory: no
    # Range: 0-1024
    # Default:
    # LogFileSize=1
    
    LogFileSize=0
    
    ### Option: DebugLevel
    #       Specifies debug level
    #       0 - no debug
    #       1 - critical information
    #       2 - error information
    #       3 - warnings
    #       4 - for debugging (produces lots of information)
    #
    # Mandatory: no
    # Range: 0-4
    # Default:
    # DebugLevel=3
    
    ### Option: PidFile
    #       Name of PID file.
    #
    # Mandatory: no
    # Default:
    # PidFile=/tmp/zabbix_server.pid
    
    PidFile=/var/run/zabbix/zabbix_server.pid
    
    ### Option: DBHost
    #       Database host name.
    #       If set to localhost, socket is used for MySQL.
    #       If set to empty string, socket is used for PostgreSQL.
    #
    # Mandatory: no
    # Default:
    DBHost=localhost
    
    ### Option: DBName
    #       Database name.
    #       For SQLite3 path to database file must be provided. DBUser and DBPassword are ignored.
    #
    # Mandatory: yes
    # Default:
    # DBName=
    
    DBName=zabbix
    
    ### Option: DBSchema
    #       Schema name. Used for IBM DB2.
    #
    # Mandatory: no
    # Default:
    # DBSchema=
    
    ### Option: DBUser
    #       Database user. Ignored for SQLite.
    #
    # Mandatory: no
    # Default:
    # DBUser=
    
    DBUser=zabbix
    
    ### Option: DBPassword
    #       Database password. Ignored for SQLite.
    #       Comment this line if no password is used.
    #
    # Mandatory: no
    # Default:
    DBPassword=zabbix
    
    ### Option: DBSocket
    #       Path to MySQL socket.
    #
    # Mandatory: no
    # Default:
    # DBSocket=/tmp/mysql.sock
    
    DBSocket=/var/lib/mysql/mysql.sock
    
    ### Option: DBPort
    #       Database port when not using local socket. Ignored for SQLite.
    #
    # Mandatory: no
    # Range: 1024-65535
    # Default (for MySQL):
    # DBPort=3306
    
    ############ ADVANCED PARAMETERS ################
    
    ### Option: StartPollers
    #       Number of pre-forked instances of pollers.
    #
    # Mandatory: no
    # Range: 0-1000
    # Default:
    StartPollers=50
    
    ### Option: StartIPMIPollers
    #       Number of pre-forked instances of IPMI pollers.
    #
    # Mandatory: no
    # Range: 0-1000
    # Default:
    # StartIPMIPollers=0
    
    ### Option: StartPollersUnreachable
    #       Number of pre-forked instances of pollers for unreachable hosts (including IPMI).
    #
    # Mandatory: no
    # Range: 0-1000
    # Default:
    StartPollersUnreachable=25
    
    ### Option: StartTrappers
    #       Number of pre-forked instances of trappers.
    #       Trappers accept incoming connections from Zabbix sender, active agents, active proxies and child nodes.
    #       At least one trapper process must be running to display server availability in the frontend.
    #
    # Mandatory: no
    # Range: 0-1000
    # Default:
    # StartTrappers=5
    
    ### Option: StartPingers
    #       Number of pre-forked instances of ICMP pingers.
    #
    # Mandatory: no
    # Range: 0-1000
    # Default:
     StartPingers=10
    
    ### Option: StartDiscoverers
    #       Number of pre-forked instances of discoverers.
    #
    # Mandatory: no
    # Range: 0-250
    # Default:
    # StartDiscoverers=1
    
    ### Option: StartHTTPPollers
    #       Number of pre-forked instances of HTTP pollers.
    #
    # Mandatory: no
    # Range: 0-1000
    # Default:
    # StartHTTPPollers=1
    
    ### Option: JavaGateway
    #       IP address (or hostname) of Zabbix Java gateway.
    #       Only required if Java pollers are started.
    #
    # Mandatory: no
    # Default:
    # JavaGateway=
    
    ### Option: JavaGatewayPort
    #       Port that Zabbix Java gateway listens on.
    #
    # Mandatory: no
    # Range: 1024-32767
    # Default:
    # JavaGatewayPort=10052
    
    ### Option: StartJavaPollers
    #       Number of pre-forked instances of Java pollers.
    #
    # Mandatory: no
    # Range: 0-1000
    # Default:
    # StartJavaPollers=0
    
    ### Option: SNMPTrapperFile
    #       Temporary file used for passing data from SNMP trap daemon to the server.
    #       Must be the same as in zabbix_trap_receiver.pl or SNMPTT configuration file.
    #
    # Mandatory: no
    # Default:
    # SNMPTrapperFile=/tmp/zabbix_traps.tmp
    
    SNMPTrapperFile=/var/log/snmptt/snmptt.log
    
    ### Option: StartSNMPTrapper
    #       If 1, SNMP trapper process is started.
    #
    # Mandatory: no
    # Range: 0-1
    # Default:
    # StartSNMPTrapper=0
    
    ### Option: ListenIP
    #       List of comma delimited IP addresses that the trapper should listen on.
    #       Trapper will listen on all network interfaces if this parameter is missing.
    #
    # Mandatory: no
    # Default:
    # ListenIP=0.0.0.0
    
    # ListenIP=127.0.0.1
    
    ### Option: HousekeepingFrequency
    #       How often Zabbix will perform housekeeping procedure (in hours).
    #       Housekeeping is removing unnecessary information from history, alert, and alarms tables.
    #
    # Mandatory: no
    # Range: 1-24
    # Default:
    # HousekeepingFrequency=1
    
    ### Option: MaxHousekeeperDelete
    #       The table "housekeeper" contains "tasks" for housekeeping procedure in the format:
    #       [housekeeperid], [tablename], [field], [value].
    #       No more than 'MaxHousekeeperDelete' rows (corresponding to [tablename], [field], [value])
    #       will be deleted per one task in one housekeeping cycle.
    #       SQLite3 does not use this parameter, deletes all corresponding rows without a limit.
    #       If set to 0 then no limit is used at all. In this case you must know what you are doing!
    #
    # Mandatory: no
    # Range: 0-1000000
    # Default:
    # MaxHousekeeperDelete=500
    
    ### Option: DisableHousekeeping
    #       If set to 1, disables housekeeping.
    #
    # Mandatory: no
    # Range: 0-1
    # Default:
    # DisableHousekeeping=0
    
    ### Option: SenderFrequency
    #       How often Zabbix will try to send unsent alerts (in seconds).
    #
    # Mandatory: no
    # Range: 5-3600
    # Default:
    # SenderFrequency=30
    
    ### Option: CacheSize
    #       Size of configuration cache, in bytes.
    #       Shared memory size for storing host, item and trigger data.
    #
    # Mandatory: no
    # Range: 128K-2G
    # Default:
    CacheSize=12M
    
    ### Option: CacheUpdateFrequency
    #       How often Zabbix will perform update of configuration cache, in seconds.
    #
    # Mandatory: no
    # Range: 1-3600
    # Default:
    # CacheUpdateFrequency=60
    
    ### Option: StartDBSyncers
    #       Number of pre-forked instances of DB Syncers
    #
    # Mandatory: no
    # Range: 1-100
    # Default:
    # StartDBSyncers=4
    
    ### Option: HistoryCacheSize
    #       Size of history cache, in bytes.
    #       Shared memory size for storing history data.
    #
    # Mandatory: no
    # Range: 128K-2G
    # Default:
    # HistoryCacheSize=8M
    
    ### Option: TrendCacheSize
    #       Size of trend cache, in bytes.
    #       Shared memory size for storing trends data.
    #
    # Mandatory: no
    # Range: 128K-2G
    # Default:
    # TrendCacheSize=4M
    
    ### Option: HistoryTextCacheSize
    #       Size of text history cache, in bytes.
    #       Shared memory size for storing character, text or log history data.
    #
    # Mandatory: no
    # Range: 128K-2G
    # Default:
    # HistoryTextCacheSize=16M
    
    ### Option: NodeNoEvents
    #       If set to '1' local events won't be sent to master node.
    #       This won't impact ability of this node to propagate events from its child nodes.
    #
    # Mandatory: no
    # Range: 0-1
    # Default:
    # NodeNoEvents=0
    
    ### Option: NodeNoHistory
    #       If set to '1' local history won't be sent to master node.
    #       This won't impact ability of this node to propagate history from its child nodes.
    #
    # Mandatory: no
    # Range: 0-1
    # Default:
    # NodeNoHistory=0
    
    ### Option: Timeout
    #       Specifies how long we wait for agent, SNMP device or external check (in seconds).
    #
    # Mandatory: no
    # Range: 1-30
    # Default:
    # Timeout=3
    
    ### Option: TrapperTimeout
    #       Specifies how many seconds trapper may spend processing new data.
    #
    # Mandatory: no
    # Range: 1-300
    # Default:
    # TrapperTimeout=300
    
    ### Option: UnreachablePeriod
    #       After how many seconds of unreachability treat a host as unavailable.
    #
    # Mandatory: no
    # Range: 1-3600
    # Default:
    # UnreachablePeriod=45
    
    ### Option: UnavailableDelay
    #       How often host is checked for availability during the unavailability period, in seconds.
    #
    # Mandatory: no
    # Range: 1-3600
    # Default:
    # UnavailableDelay=60
    
    ### Option: UnreachableDelay
    #       How often host is checked for availability during the unreachability period, in seconds.
    #
    # Mandatory: no
    # Range: 1-3600
    # Default:
    # UnreachableDelay=15
    
    ### Option: AlertScriptsPath
    #       Full path to location of custom alert scripts.
    #       Default depends on compilation options.
    #
    # Mandatory: no
    # Default:
    # AlertScriptsPath=${datadir}/zabbix/alertscripts
    
    AlertScriptsPath=/usr/lib/zabbix/alertscripts
    
    ### Option: ExternalScripts
    #       Full path to location of external scripts.
    #       Default depends on compilation options.
    #
    # Mandatory: no
    # Default:
    # ExternalScripts=${datadir}/zabbix/externalscripts
    
    ExternalScripts=/usr/lib/zabbix/externalscripts
    
    ### Option: FpingLocation
    #       Location of fping.
    #       Make sure that fping binary has root ownership and SUID flag set.
    #
    # Mandatory: no
    # Default:
    # FpingLocation=/usr/sbin/fping
    
    ### Option: Fping6Location
    #       Location of fping6.
    #       Make sure that fping6 binary has root ownership and SUID flag set.
    #       Make empty if your fping utility is capable to process IPv6 addresses.
    #
    # Mandatory: no
    # Default:
    # Fping6Location=/usr/sbin/fping6
    
    ### Option: SSHKeyLocation
    #       Location of public and private keys for SSH checks and actions
    #
    # Mandatory: no
    # Default:
    # SSHKeyLocation=
    
    ### Option: LogSlowQueries
    #       How long a database query may take before being logged (in milliseconds).
    #       Only works if DebugLevel set to 3 or 4.
    #       0 - don't log slow queries.
    #
    # Mandatory: no
    # Range: 1-3600000
    # Default:
    # LogSlowQueries=0
    
    ### Option: TmpDir
    #       Temporary directory.
    #
    # Mandatory: no
    # Default:
    # TmpDir=/tmp
    
    ### Option: Include
    #       You may include individual files or all files in a directory in the configuration file.
    #       Installing Zabbix will create include directory in /usr/local/etc, unless modified during the compile time.
    #
    # Mandatory: no
    # Default:
    # Include=
    
    # Include=/usr/local/etc/zabbix_server.general.conf
    # Include=/usr/local/etc/zabbix_server.conf.d/
    
    ### Option: StartProxyPollers
    #       Number of pre-forked instances of pollers for passive proxies.
    #
    # Mandatory: no
    # Range: 0-250
    # Default:
    # StartProxyPollers=1
    
    ### Option: ProxyConfigFrequency
    #       How often Zabbix Server sends configuration data to a Zabbix Proxy in seconds.
    #       This parameter is used only for proxies in the passive mode.
    #
    # Mandatory: no
    # Range: 1-3600*24*7
    # Default:
    # ProxyConfigFrequency=3600
    
    ### Option: ProxyDataFrequency
    #       How often Zabbix Server requests history data from a Zabbix Proxy in seconds.
    #       This parameter is used only for proxies in the passive mode.
    #
    # Mandatory: no
    # Range: 1-3600
    # Default:
    # ProxyDataFrequency=1
    Last edited by dumi; 05-01-2015, 16:28.
  • tchjts1
    Senior Member
    • May 2008
    • 1605

    #2
    See this post: https://www.zabbix.com/forum/showthread.php?t=47781

    May be time to increase your HistoryCacheSize= setting.

    Comment

    • dumi
      Junior Member
      • Dec 2014
      • 7

      #3
      Thank you tchjts1, i increase HistoryCacheSize from 8M to 12M, my hardware is modest and i don't want to kill the cpu. For now it's looking good, i will let it run for a week to see if the problem was solved.

      Comment

      • tchjts1
        Senior Member
        • May 2008
        • 1605

        #4
        Define "modest".
        My setup runs on VM's. Looking at your graphs, I see some other values I would increase as well.

        Comment

        • dumi
          Junior Member
          • Dec 2014
          • 7

          #5
          I run zabbix also on VM with following specifications:

          CPU: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz,
          cpu cores : 4

          RAM: 512 MB

          What are the other value, you make me interested?

          P.S.: When housekeeper is running the cpu reaches 70 - 80 % (the mysql eats most of the resource)

          Comment

          • tchjts1
            Senior Member
            • May 2008
            • 1605

            #6
            512M memory is very limiting. You can't give those VM's some more memory?

            You are not running your DB and Zabbix server on the same VM are you?

            The other values I would increment are CacheSize= and I would allocate a slightly larger number of StartPollers=

            That small amount of memory in your VM has you constrained though.

            That is normal for housekeeper to hit high % busy when it runs.

            Comment

            • dumi
              Junior Member
              • Dec 2014
              • 7

              #7
              The DB and the zabbix is on the same VM. Unfortunately on the physical server where is zabbix vm we have other vm's and this is all the ram i can give to zabbix for the moment.

              Comment

              • joszif
                Junior Member
                • Jan 2018
                • 5

                #8
                same problem with zabbix 3.4.6

                Hello,

                I have the same problem, but a standalone zabbix server (ver 3.4.6, no proxies). The zabbix server and mysql (ver 5.7) run on the same machine. The server is a virtual machine, run on vmware (esxi6.5)
                I get alarms in every hours, about history syncer: "history syncer processes more than 75% busy". And zabbix agent on server is unreachable for 5 minutes.

                Zabbix server monitor 100 routers/switches via snmp (polling) and 5 vmware host.


                virtual machine params:

                4vCPU
                12Gb RAM
                128Gb HDD

                Ubuntu 16.04


                zabbix_server.conf:


                LogFile=/var/log/zabbix/zabbix_server.log
                LogFileSize=0
                PidFile=/var/run/zabbix/zabbix_server.pid
                SocketDir=/var/run/zabbix
                StartPollers=20
                StartPollersUnreachable=10
                StartPingers=10
                StartDiscoverers=10
                SNMPTrapperFile=/tmp/zabbix_traps.tmp
                StartSNMPTrapper=1
                CacheSize=128M
                StartDBSyncers=4
                HistoryCacheSize=128M
                HistoryIndexCacheSize=128M
                TrendCacheSize=16M
                ValueCacheSize=64M
                Timeout=4
                AlertScriptsPath=/usr/lib/zabbix/alertscripts
                ExternalScripts=/usr/lib/zabbix/externalscripts
                FpingLocation=/usr/bin/fping
                Fping6Location=/usr/bin/fping6
                LogSlowQueries=3000


                mysql.cnf:


                [mysqld_safe]
                socket = /var/run/mysqld/mysqld.sock
                nice = 0
                [mysqld]
                user = mysql
                pid-file = /var/run/mysqld/mysqld.pid
                socket = /var/run/mysqld/mysqld.sock
                port = 3306
                basedir = /usr
                datadir = /var/lib/mysql
                tmpdir = /tmp
                lc-messages-dir = /usr/share/mysql
                skip-external-locking
                bind-address = 127.0.0.1
                key_buffer_size = 16M
                max_allowed_packet = 16M
                thread_stack = 192K
                thread_cache_size = 8
                myisam-recover-options = BACKUP
                query_cache_limit = 1M
                log_error = /var/log/mysql/error.log
                expire_logs_days = 10
                max_binlog_size = 100M
                innodb_buffer_pool_size = 8G
                innodb_buffer_pool_instances=16
                innodb_flush_log_at_trx_commit = 0
                innodb_flush_method = O_DIRECT
                innodb_log_file_size = 128M
                innodb_read_io_threads = 8
                innodb_write_io_threads = 8
                innodb_old_blocks_time = 1000
                innodb_io_capacity = 300
                sync_binlog=0
                query_cache_size=0
                query_cache_type=0

                Comment

                • BSDUKJ
                  Member
                  • Aug 2017
                  • 38

                  #9
                  Hi Joszif,

                  I had something similar with 3.4.5,

                  I changed the following in zabbix_server.conf

                  StartPollers=50
                  StartPollersUnreachable=50
                  CacheSize=2G
                  Timeout=15

                  In mysql.cnf

                  max_connections=500

                  I think it was the max_connections that resolved it.

                  See the thread here: see https://www.zabbix.com/forum/showthread.php?t=60263

                  Comment

                  • kloczek
                    Senior Member
                    • Jun 2006
                    • 1771

                    #10
                    In most cases when history syncers utilisation is high, it means that DB backend performance is not enough (mostly on insert queries which are causing write IOs)
                    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

                    • kaspars.mednis
                      Senior Member
                      Zabbix Certified Trainer
                      Zabbix Certified SpecialistZabbix Certified Professional
                      • Oct 2017
                      • 349

                      #11
                      3.4.5 and 3.4.6 are affected by


                      that can be the cause of your issue

                      Regards,
                      Kaspars

                      Comment

                      • joszif
                        Junior Member
                        • Jan 2018
                        • 5

                        #12
                        Hi,

                        Thank you BSDUKJ, I increased the values in zabbix_server.conf and mysql max_connections but unfortunately same result. The concurrent mysql connections are around 80.
                        When the history syncer process run, the iowait (mysql process) is high, around ~90% and load is 4. And I get the alarm "history syncer processes more than 75% busy".

                        Thanks Kaspars, We waiting for release 3.4.7 and we will test it.

                        joszif

                        Comment

                        • kloczek
                          Senior Member
                          • Jun 2006
                          • 1771

                          #13
                          Originally posted by joszif
                          Hi,

                          Thank you BSDUKJ, I increased the values in zabbix_server.conf and mysql max_connections but unfortunately same result. The concurrent mysql connections are around 80.
                          When the history syncer process run, the iowait (mysql process) is high, around ~90% and load is 4. And I get the alarm "history syncer processes more than 75% busy".

                          Thanks Kaspars, We waiting for release 3.4.7 and we will test it.

                          joszif
                          You are not exceeding max_connections so increase it does not make any sense.

                          Hifg IO wait is clear indicator that your problem is slow storage.
                          Look at the ratio between read and write IOs.
                          If you have the majority of reads you need more PHYSICAL memory which will allow buffer necessary DB files in buffer cache or straight use this additional memory to increase innodb memory pool.
                          If you have majority of the write operations and IO wait still is high it means that physical storage used by DB backend is not enough fast. By this, you have the bottleneck in write operations (mainly inserts). This type of issue is not about write bandwidth but about write IO latency.

                          With correctly chosen memory size available for DB backend most of the selects should be served out from data cached in memory. If this memory footprint is enough you should be able to observe at least 1:20 ratio between read and write IOs.
                          Giving enough memory for DB backend is crucial as well to have lowest possible inserts queries latency as always insert before starts to write physical IOs is doing a couple of read IOs to locate where newly inserted data needs to be written.
                          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

                          • joszif
                            Junior Member
                            • Jan 2018
                            • 5

                            #14
                            Hi Kloczek,

                            Ok, the storage performance problem is clear but I made some test with dd, ioping and the performance seems to be "good".

                            bi@zabbix:/tmp$ dd if=/dev/zero of=/tmp/testfile bs=1G count=1 oflag=direct
                            1+0 records in
                            1+0 records out
                            1073741824 bytes (1,1 GB, 1,0 GiB) copied, 2,58232 s, 416 MB/s


                            bi@zabbix:/tmp$ ioping -S64M -L -s4K -W -c 15 .
                            4 KiB to . (ext4 /dev/sda1): request=1 time=230 us
                            4 KiB to . (ext4 /dev/sda1): request=2 time=206 us
                            4 KiB to . (ext4 /dev/sda1): request=3 time=181 us
                            4 KiB to . (ext4 /dev/sda1): request=4 time=188 us
                            4 KiB to . (ext4 /dev/sda1): request=5 time=196 us
                            4 KiB to . (ext4 /dev/sda1): request=6 time=189 us
                            4 KiB to . (ext4 /dev/sda1): request=7 time=207 us
                            4 KiB to . (ext4 /dev/sda1): request=8 time=199 us
                            4 KiB to . (ext4 /dev/sda1): request=9 time=182 us
                            4 KiB to . (ext4 /dev/sda1): request=10 time=181 us
                            4 KiB to . (ext4 /dev/sda1): request=11 time=204 us
                            4 KiB to . (ext4 /dev/sda1): request=12 time=279 us
                            4 KiB to . (ext4 /dev/sda1): request=13 time=215 us
                            4 KiB to . (ext4 /dev/sda1): request=14 time=289 us
                            4 KiB to . (ext4 /dev/sda1): request=15 time=203 us

                            --- . (ext4 /dev/sda1) ioping statistics ---
                            15 requests completed in 14.0 s, 4.76 k iops, 18.6 MiB/s
                            min/avg/max/mdev = 181 us / 209 us / 289 us / 31 us


                            bi@zabbix:/tmp$ ioping -A -D -s16K -c 10 .
                            16 KiB from . (ext4 /dev/sda1): request=1 time=165 us
                            16 KiB from . (ext4 /dev/sda1): request=2 time=226 us
                            16 KiB from . (ext4 /dev/sda1): request=3 time=266 us
                            16 KiB from . (ext4 /dev/sda1): request=4 time=219 us
                            16 KiB from . (ext4 /dev/sda1): request=5 time=274 us
                            16 KiB from . (ext4 /dev/sda1): request=6 time=251 us
                            16 KiB from . (ext4 /dev/sda1): request=7 time=222 us
                            16 KiB from . (ext4 /dev/sda1): request=8 time=291 us
                            16 KiB from . (ext4 /dev/sda1): request=9 time=257 us
                            16 KiB from . (ext4 /dev/sda1): request=10 time=279 us

                            --- . (ext4 /dev/sda1) ioping statistics ---
                            10 requests completed in 9.00 s, 4.08 k iops, 63.8 MiB/s
                            min/avg/max/mdev = 165 us / 245 us / 291 us / 35 us



                            The output of the mysql "show processlist" command show that much of the mysql processes are in sleep state, only 3-4 query (selects) running...
                            I increased the phisycal memory from 12Gb to 16Gb. But currently, the size of the database is around 50Gb, so I think the memory is not enough and innodb_buffer_pool_size is should be increase too?!

                            joszif.

                            Comment

                            • kloczek
                              Senior Member
                              • Jun 2006
                              • 1771

                              #15
                              Quote "Look at the ratio between read and write IOs."
                              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

                              Working...