Forum Discussion
Default retry time inband monitor
I could see this causing an issue if you have multiple monitors and some sort of rate limiting on the server side. In addition, depending on the monitor, you will be opening a new connection every time you run the monitor. This becomes an even larger issue if you have thousands of health monitors running simultaneously but at low pool member/monitor levels it shouldn't really be an issue.
when the monitor runs simultaneously, will it cause disruption to server side traffic? I think when the monitor runs every 1 second it will bring good performance to find out the server condition faster.
isn't it when the retry becomes 300 seconds, and the monitor is up in less than that time, does it mean that there is ineffectiveness in the use of server resources that are actually available?
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com