MattiasN81
Hot Shot
Hot Shot

There are several factors that comes into play here.

SIOC itself only acts on ESXi workloads and not other workloads handled by other storage operations such as RAID rebuilds, CIFS workloads and so on, in your case according to the message "An unmanaged I/O workload is detected on a SIOC-enabled datastore"  SIOC detected a workload above specified threshold (25ms) but because ESXi detected the workload as non-esxi workload SIOC couldn't do anything with it other than report it.

Here is where the tricky part comes in.

In this case is actually was a VM that caused the high latency witch we deadly humans wound would say "Hey, a VM caused it so its sure as hell an esxi workload" well thats not entirely true.

Depending what type of workload and how the storage array handles it plays a part how SIOC will react on it.therefore is crucial to have an array/solution that is supported with SIOC

I can take an example from my own experience with SIOC and an EMC array running an unsupported setup with auto-tiering and FAST cache

The problem was the same as yours, a VM did some stuff that resulted in high latency, the problem wasn't the VMs workload perse but when the VM started to do its thing the storage array did what it was supposed to do, place hot data in the cache move cold data to disks and kick in a tiering job, due to the extremely high workload on the VM the array couldn't keep up and the result was from VMwares perspective high latency on that datastore but SIOC couldn't do anything because is was never the VMs that caused the latency but storage operations in the backend.

I hopes this clarify a little how SIOC operates

VMware Certified Professional 6 - DCV VMware VTSP Software Defined Storage Dell Blade Server Solutions - EMEA Certified Dell PowerEdge Server Solutions - EMEA Certfied Dell Certified Storage Deployment Professional Dell EMC Proven Professional If you found my answers useful please consider marking them as Helpful or Correct

View solution in original post