On Tue, Aug 02, 2011 at 03:08:32PM -0400, James Bardin wrote:
> > - the server does not have the SRV_RUNNING flag in maintenance mode
> > - the "persist" option on the backend might be one reason
> > - I'm assuming there is no "force-persist" rule
> >
>
> OK, that's it.
Fine!
> I didn't realize
On Tue, Aug 2, 2011 at 2:44 PM, Willy Tarreau wrote:
>
> OK thanks for confirming. Could you check if you have "option persist"
> somewhere in your config ? From what I can tell from the code, this is
> the only reason why a server set in maintenance mode would be selected :
>
> if ((srv->
On Tue, Aug 02, 2011 at 09:00:08AM -0400, James Bardin wrote:
> On Tue, Aug 2, 2011 at 2:52 AM, Willy Tarreau wrote:
>
> >
> > Are you sure your server was set in maintenance mode, did you not just
> > set its weight to zero ?
> >
>
> Yes. I've confirmed that when using a stick-table for persist
On Tue, Aug 2, 2011 at 2:52 AM, Willy Tarreau wrote:
>
> Are you sure your server was set in maintenance mode, did you not just
> set its weight to zero ?
>
Yes. I've confirmed that when using a stick-table for persistence,
putting a server in maintenance mode does not block traffic from
existin
Hi James,
On Mon, Aug 01, 2011 at 04:05:41PM -0400, James Bardin wrote:
> I have a number if instances using tcp mode, and a stick-table on src
> ip for affinity. When a server is in maintenance mode, clients with an
> existing affinity will still connect to the disabled server, and only
> be re-d
I have a number if instances using tcp mode, and a stick-table on src
ip for affinity. When a server is in maintenance mode, clients with an
existing affinity will still connect to the disabled server, and only
be re-dispatched if the connection fails (and error responses from the
backend are still
6 matches
Mail list logo
