I have tried to reproduce the bug with the environment that you reported:
-> almost a thousand shares
-> more than hundred share servers
-> 2 backends
-> 30 mounted shares with users writing and erasing data constantly
-> decreasing the time for updating metrics (instead of 60, 10 seconds)
Look at the log during a long period of time, I could not get the "Timeout" reported error, though.
It might have something in your production manila that we cannot reproduce in our lab.
Given that it is a ONTAP error, we are working in a workaround for catching the error and setting it for the default utilization metrics. some questions:
-> Are you using the 'utilization' for filter e goodness functions ?
Hi maurice,
I have tried to reproduce the bug with the environment that you reported:
-> almost a thousand shares
-> more than hundred share servers
-> 2 backends
-> 30 mounted shares with users writing and erasing data constantly
-> decreasing the time for updating metrics (instead of 60, 10 seconds)
Look at the log during a long period of time, I could not get the "Timeout" reported error, though.
It might have something in your production manila that we cannot reproduce in our lab.
Given that it is a ONTAP error, we are working in a workaround for catching the error and setting it for the default utilization metrics. some questions:
-> Are you using the 'utilization' for filter e goodness functions ?
-> How often the error occur ?
Best regards, Felipe.