Jump to content


Load agent is caching DNS


  • Please log in to reply
1 reply to this topic

#1 Guest_rpillen_*

Guest_rpillen_*
  • Guests

Posted 30 July 2009 - 09:20 AM

To explain our problem, we first need to explain the setup we're using.

We got a SharePoint farm (2 WFE's, 2 Application Servers, 1 SQL server) with ISA 2006 as Reverse Proxy. Running stress tests gave us insight in that our ISA server wasn't sufficient for our load (up to 900 users), so we decided to setup a second ISA server and let 3DNS balance the load over the 2 ISA servers. (30 seconds intervals)

While our requests from our client were referenced to the right ISA machines (swiched every 30 seconds), all requests from the load-test were pointed to the same ISA machine. Even in a new load-test, they were still pointed to the sole ISA machine. After restarting the WAPT Agent, the requests were sent to the other machine, but then the first machine didn't receive requests anymore.

We can't continually restart the Load agent on every swap of our 3DNS.
I think the Load agent caches the DNS and just sends requests to IP-addresses. In our setup with 3DNS load balancing that is not sufficient.
Please look into it.

Thanks in advance
R. Pillen

#2 Guest_angela_*

Guest_angela_*
  • Guests

Posted 30 July 2009 - 01:03 PM

QUOTE (rpillen @ Jul 30 2009, 04:20 PM) <{POST_SNAPBACK}>
To explain our problem, we first need to explain the setup we're using.

We got a SharePoint farm (2 WFE's, 2 Application Servers, 1 SQL server) with ISA 2006 as Reverse Proxy. Running stress tests gave us insight in that our ISA server wasn't sufficient for our load (up to 900 users), so we decided to setup a second ISA server and let 3DNS balance the load over the 2 ISA servers. (30 seconds intervals)

While our requests from our client were referenced to the right ISA machines (swiched every 30 seconds), all requests from the load-test were pointed to the same ISA machine. Even in a new load-test, they were still pointed to the sole ISA machine. After restarting the WAPT Agent, the requests were sent to the other machine, but then the first machine didn't receive requests anymore.

We can't continually restart the Load agent on every swap of our 3DNS.
I think the Load agent caches the DNS and just sends requests to IP-addresses. In our setup with 3DNS load balancing that is not sufficient.
Please look into it.

Thanks in advance
R. Pillen


Hello,

We are going to implement the option which will allow enabling\disabling DNS caching. It will be implemented in our newer version.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users