![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||||
Solution Type Problem Resolution Sure Solution 1588767.1 : Pillar Axiom: Storage System Axiom General Configuration Issues
Settings for throttling queue depth in VMWare ESX/ESXi In this Document
Created from <SR 3-7823472850> Applies to:Pillar Axiom 600 Storage System - Version All Versions and laterPillar Axiom 300 Storage System - Version All Versions and later Pillar Axiom 500 Storage System - Version All Versions and later Information in this document applies to any platform. If a VMWare ESX 3.x host detects a queue full condition, it may abort the SCSI commands. VMWare ESX/ESXi 4.0 and higher will display a device busy error. SymptomsIf QFULL conditions exist, the ESX VMkernel log may contain entries similar to:
The hexadecimal 28 or decimal 40 in the error is the SCSI status code for the queue full state. The value 0x08 in the above error is the SCSI Status code indicating a device busy state.
ChangesNone. CauseIO is heavier than queue depth allows. SolutionVMware ESX 3.5 Update 4 introduces an adaptive queue depth algorithm that adjusts the LUN queue depth in the VMkernel I/O stack. This algorithm is activated when the storage array indicates I/O congestion by returning a BUSY or QUEUE FULL status. These status codes may indicate congestion at the LUN level or at the port (or ports) on the array. When congestion is detected, VMkernel throttles the LUN queue depth. The VMkernel attempts to gradually restore the queue depth when congestion conditions subside. QFullSampleSize to a value greater than zero. The usable range is 0 to 64. For Pillar Axiom arrays the recommended value would be 32. References<BUG:15904168> - ESXI4U2 VMS CRASHED DUE TO TIMEOUTS - NEED QFULLSAMPLESIZE & QFULLTHRESHOLD RECOhttp://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1008113 Attachments This solution has no attachment |
||||||||||||||||||||
|