Large number of vxiod processes observed in 'ps' output on InfoScale 7.4.1/RHEL7 GCO/VVR environments.
Article ID: 100053914
Updated On:
Description
Error Message
N/A
Cause
With Veritas Volume Manager (VxVM) 7.3, the vxiod implementation was redesigned to reduce lock contention. VxVM worker threads (VxVM IOD's) are used to process IOs in the current context.
For example, when DRL (Dirty Region Log) logging is required for IO or when VVR is configured, an application write needs to be scheduled using VxVM worker threads.
In order to reduce lock contention each IOD has its own work-queue and lock and the IOD would be selected from a pool of IODs and the IO would be queued there.
Resolution
For systems with up to 8 CPUs, it is expected that they will automatically have 32 (16 + 16) vxiods in the 'ps' output. This would be true for systems with 4 CPUs as well as systems with 8 CPUs.
For systems with more than 8 CPUs, it is expected to see 16+(# of CPUs * 2) vxiods in the 'ps' output.
The same behaviour should be observed in VxVM 7.3 and above.
Issue/Introduction
Additional Information
