问题原文
原帖链接 · zavg · CC BY-SA 4.0
I have multiple processes running simultaneously on the same box under CentOS 7 (each one on behalf of the separate Linux user).
I use Zabbix for monitoring.
Sometimes the following pattern appears on CPU utilization graph.
If you zoom in, then it looks like
So the server freezes for some time, and even SSH login does not work (as well as other processes are not working as expected, of course) and Zabbix agent fails to send its data to Zabbix server (Zabbix server is located on separate host).
As I understand from the Zabbix legend the yellow part of the chart is iowait.
So could you explain how the iowait of one process can affect the whole system so drastically?
And how is it possible to prevent and to restrict this behaviour?
已采纳解答
原帖链接 · TomTom · CC BY-SA 4.0
It is not a process, it is the time things are waiting for IO.
I would say you possibly have a hard disc there that is totally overloaded at those times. Like ridiculously overloaded - possibly by:
- Extremely bad programming that does not buffer things in memory.
- Extremely bad hardware selection (i.e. a hard disc where there simply is not enough IO budget and a SSD is needed).
- Extremely faulty hardware (bad sectors on a HD) that make it go into some sort of retry pattern that takes some time.
- Standard usage. If you have a database that does reorganize indices it will try t do so as fast as possible and it is possible to cause serious IO spikes regardless what hardware you throw at it.
OBVIOUSLY it could also be some software bug in a driver, but given that this is a pro forum I would assume you have made sure to be current on service packs.
You will have to start analyzing what is happening that causes excessive IO. I.e. you have to look at the IO wait statistics of the processes, not the system totals.
Given that a LOT of things are doing IO - and often wait for it to complete - it is not surprising that a total IO overload causes all kinds of weird behavior.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
