
UNSOLVED
path_latency_threshold: Why only in Seconds? Anyone using it effectively?
I was excited to learn about this powerpath feature only to see that's it not very useful. I'm hoping someone is finding it useful.
If a system is normally running at 10ms or less for all I/O, it would be nice to know when it goes to 15 or more and, try to resolve it proactively.
The path_latency_threshold seems to work only 1 sec increments. Setting it would only log a notification in the system log when the I/O goes to 1000ms or more. This does not seem very useful in reality.
We get calls on applications that go from 4ms to 6ms, let alone going to 1 sec. It would be nice if this worked with milliseconds instead of seconds.
Anyone finding this parameter useful in their env?
Responses (0)
Solutions (0)
