Forum Discussion

GIS1STOP_182395's avatar
GIS1STOP_182395
Icon for Nimbostratus rankNimbostratus
Jan 12, 2015

Does LTM really support Zero downtime?

In web application system, there are two IIS web servers running the same web site. Above them, there is one LTM as load balancer. I was told, if one web server is shutdown, it will take up to 90 seconds for LTM knowing the one web server is shutdown and then redirect future requests. So during that 90 seconds, some requests to our web site will fail.

 

According to LTM product page: https://f5.com/products/modules/local-traffic-manager. It could be zero down time. How can I tell my LTM administrator to configure LTM so that when one web server is failed, all request will immediately redirect to the another running web server?

 

Thanks

 

  • Hi, the monitor interval and timeout settings are user configurable. You could set the interval for one second and the timeout for 4 seconds, after which a connection load balanced to that downed pool member would be handled according to the "Action on Service Down" setting in the pool configuration.

     

    Too aggressive interval/timeout settings will probably put too much traffic on the wire and too much load on your servers...you'll want to adjust them appropriately for your application.

     

    If you are using the IIS iApp, the template does default to 30/91 for interval/timeout, but allows you to specify the monitor interval and adjusts the timeout to (interval x3) + 1 second. If you use a 5 second interval, the timeout will be 16 seconds.

     

  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account

    Hi, the monitor interval and timeout settings are user configurable. You could set the interval for one second and the timeout for 4 seconds, after which a connection load balanced to that downed pool member would be handled according to the "Action on Service Down" setting in the pool configuration.

     

    Too aggressive interval/timeout settings will probably put too much traffic on the wire and too much load on your servers...you'll want to adjust them appropriately for your application.

     

    If you are using the IIS iApp, the template does default to 30/91 for interval/timeout, but allows you to specify the monitor interval and adjusts the timeout to (interval x3) + 1 second. If you use a 5 second interval, the timeout will be 16 seconds.

     

  • JG's avatar
    JG
    Icon for Cumulonimbus rankCumulonimbus

    On caveat is that if you configure you monitor to run too frequently, you might run into an issue of port exhaustion, or a port re-use issue. You might need to match / tune the network stack of your app server for this to work.