IIS 7 and Above
Application Request Routing (ARR)
Load Balancer L4 (keepalived) + ARR Farm
Last post Oct 01, 2018 10:57 PM by fben
Sep 30, 2018 06:38 PM|fben|LINK
Good afternoon, under what circumstances do you consider that ARR does not respect the established timeout time in your proxy settings?
It turns out that I am generating problems when I enter a requirement through an L4 balancer whose destination is an ARR farm, request
them not only if one sees the process they are hung adding time but also do not fall by the time out specified in the proxy configuration .
If the requirement enters directly to one of the ARRs of the farm, the behavior is perfect.
Can you think of something?
Thank you so much.
Oct 01, 2018 06:11 AM|Terry Peng|LINK
To be honest, I can hardly understand what do you mean "request
them not only if one sees the process they are hung adding time but also do not fall by the time out specified in the proxy configuration".
I would suggest you share some details to explain what happened to you so we could understand your issue more exactly.
Please note that there are two different proxy settings, one is for ARR and one is for your server farm.
What's the timeout time setting for your ARR and the timeout time for your server farm? What will happen for requests to the server farm?
Oct 01, 2018 10:57 PM|fben|LINK
Hi, thanks for your response. It may have confused you a little, maybe also because of my poor English.
Leaving the load balancer in layer 4 aside.
My ARR configuration is doing a redirect to farm according to the condition in a rule of the urlrewrite module.
Each farm has in its configuration the proxy section where a cut-off time can be set, the problem I'm having is that sometimes the farm's cut setting does not apply and the call is hung when viewed from the farm. option of the worker process explorer.
The question is: did this ever happen to you?
If you need more information, let me know.
Thank you so much.