Identifying a severely overloaded storage
When storage is severely overloaded, commands are aborted because the storage subsystem takes far too long to respond to the commands. The storage subsystem doesn't respond within an acceptable amount of time, as defined by the guest operating system or application. Aborted commands are a sign that the storage hardware is overloaded and unable to handle the requests in line with the host's expectations.
The number of aborted commands can be monitored using either vSphere Web Client or resxtop, as follows:
- From vSphere Web Client, monitor the
diskcommand aborts - From esxtop, monitor ABRTS/s
Getting ready
To step through this recipe, you will need one or more running ESXi Servers, a vCenter Server, vSphere Web Client, and an SSH Client (such as PuTTY). No other prerequisites are required.
How to do it...
To monitor the disk command aborts using vSphere Client, follow these steps:
- Open up vSphere Web Client.
- Log in to the vCenter Server.
- Navigate to the
Hosts...
