[lvs-users] in ldirectord.cf, the meaning of 'checkcount' is ambiguous
horms at verge.net.au
Thu Jul 14 10:18:03 BST 2011
On Thu, Jul 14, 2011 at 01:33:22AM -0700, Robinson, Eric wrote:
> > -----Original Message-----
> > From: Simon Horman [mailto:horms at verge.net.au]
> > Sent: Tuesday, July 12, 2011 7:56 PM
> > To: Robinson, Eric
> > Cc: lvs-users at linuxvirtualserver.org
> > Subject: Re: [lvs-users] in ldirectord.cf, the meaning of 'checkcount'
> > ambiguous
> > On Fri, Jul 08, 2011 at 04:45:17AM -0700, Robinson, Eric wrote:
> > > The ldirectord man page states that 'checkcount' only works with
> > > checks. Then the next sentence goes on to give an example of
> > > being used in conjunction with connectimeout/negotiatetimeout,
> > > of which are related to ping checks. Can someone please clarify?
> > Hi Eric,
> > sorry for not responding earlier.
> > I've taken a look at the code (in git) and to be honest I don't
> > think that this is my handiwork. But none the less I believe that
> > the situation is:
> > * checkcount only applies to ping.
> > There is a loop in the ping check that will try
> > ping up to checkcount times, breaking out of the loop
> > if a ping is successful
> > * checkcount is deprecated in favour of failurecount
> > * failurecount works similarly to checkcount, except that it
> > it operates at a higher level and applies to all types of checks
> > * It appears that specifying both failurecount and checkcount would
> > a multiplier effect, though only for ping checks
> > I will fix up the sample ldirectord.cf to make use of failurecount
> > instead of checkcount.
> That's delightful, Horms, thanks for the clarification. I don't think my
> version of ldirectord has the failurecount option. It's been in
> production since 2006 and is currently managing about 900 virtual
> services. I've never wanted to mess with it much, considering that it
> has worked very well for us. The failurecount option may be adequate
before upgrading I would check the source code to see if
checkcount (or some other option) meets your requirements.
More information about the lvs-users