Re: Setting IPVS/LVS timeout in Keepalived
"Ryan O'Hara" <[email protected]>
| Newsgroups | gmane.linux.keepalived.devel |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Dec 12, 2013 at 09:28:25AM -0500, Paul Robert Marino wrote: > On Red Hat I would put that in /etc/sysconfig/keepalived even though > thats a kludge as well its at least a little cleaner. Can you explain how this would work? > On Thu, Dec 12, 2013 at 6:25 AM, Ville Törhönen <[email protected]> wrote: > > Hello. > > > > Is it possible to configure IPVS/LVS timeout values in the Keepalived > > configuration file? By default the TCP timeout values in the kernel LVS > > tables are as follows: > > > > - TCP sessions: 900 seconds > > - TCP sessions after receiving a FIN packet: 120 seconds > > - UDP packets: 300 seconds > > > > These values can be modified via 'ipsetadm --set', for e.g. > > > > $ ipvsadm --set 3600 120 300 > > > > As expected, these modifications are not persistent and they are lost > > after system restart. If the current LVS configuration is printed out > > with 'ipsetadm-save -n', the timeout values aren't included. This makes > > it impossible to reload the timeout values with the ipvsadm init script. Right, but as I am sure you know keepalived does not care about the ipvsadm init script. We had this same issue in Piranha a while back and I ended up adding the timeouts as options in the config file. > > This has been discussed several times in the lvs-users mailing list. It > > has always come to a conclusion that LVS/IPVS is a framework and that > > the management application should do the configuring. I know that there > > are other ways to implement this, such as setting the timeout value in > > /etc/rc.local, but it's obviously a nasty kludge. I'd be happy to add this to keepalived, but I'd like some ideas on where these options would be place in the config file. The real_server blocks and the primary means to configure ipvs related in keepalived, but these timeouts are not set on a per real server basis. I'd suggest we either add a new top-level config keyword or set them in global_defs. Opinions? Ryan > > Thanks, > > Ville > > > > ------------------------------------------------------------------------------ > > Rapidly troubleshoot problems before they affect your business. Most IT > > organizations don't have a clear picture of how application performance > > affects their revenue. With AppDynamics, you get 100% visibility into your > > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! > > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk > > _______________________________________________ > > Keepalived-devel mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/keepalived-devel > > ------------------------------------------------------------------------------ > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application performance > affects their revenue. With AppDynamics, you get 100% visibility into your > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk > _______________________________________________ > Keepalived-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/keepalived-devel ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk