- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
https://kb.vmware.com/s/article/2144493?lang=en_US the KB doesnt give much detail as this can be a generic symptom of something else
This could potentially be a symtom of bursty IO, where most of the time there was no delay, but due to the bursty nature of IO workload pattern triggered some stress on the internal queues.
you may need to work back to what VMs were doing at that time to see if it was driven by temp spike on workload
But then again you are using the stretch cluster so the network can never be discounted
I would advise to attempt to characterise any sudden change in workload from the VMs
you may need to get help from support at this to attempt to narrow down where this spike is coming from.