Forum Discussion
- Vijay_ECirrus
My understanding of this: "Maximum Size setting must be at least one number smaller than the connection limit set for a pool member."
If you use "OneConnect" on multiple VS, make sure that the following condition matches: "Max Size" setting in OneConnect < Connection limit set per pool member associated with any of the VS that uses the same OneConnect profile.
I think this is provided to prevent overloading the pool member in the relatively unlikely event of all connections being sent to only one pool member. So, if Max Size is 100 and pool member connection limit for 1.1.1.1:80 is 90 and assuming no other pool member is available, it can possibly overload 1.1.1.1:80 as the OneConnect connections are persistent and not torn down when it is closed by the client.