Re: Different check conditions for server selected from lb trees

2013-08-13 Thread Willy Tarreau
Hi Godbach, On Wed, Aug 07, 2013 at 11:26:40AM +0800, Godbach wrote: > From 370a74e89af0153a96ed8b7ebd4648258c89109e Mon Sep 17 00:00:00 2001 > From: Godbach > Date: Wed, 7 Aug 2013 09:48:23 +0800 > Subject: [PATCH] BUG/MINOR: use the same check condition for server as other > algorithms (...)

Re: Different check conditions for server selected from lb trees

2013-08-06 Thread Godbach
On 2013/8/6 20:36, Willy Tarreau wrote: > Hi Godbach, > > Sorry for replying late, I don't have a regular internet access at the > moment. > > On Tue, Aug 06, 2013 at 07:48:46PM +0800, Godbach wrote: >> It seems that static-rr should also use the same check condition for the >> server after being

Re: Different check conditions for server selected from lb trees

2013-08-06 Thread Willy Tarreau
Hi Godbach, Sorry for replying late, I don't have a regular internet access at the moment. On Tue, Aug 06, 2013 at 07:48:46PM +0800, Godbach wrote: > It seems that static-rr should also use the same check condition for the > server after being selected as roundrobin and leastconn as below: > > i

Re: Different check conditions for server selected from lb trees

2013-08-06 Thread Godbach
On 2013/8/1 17:05, Godbach wrote: > Hi Willy, > > Haproxy will check the number of concurrent sessions assigned to the > server after being selected from lb trees. Both leastconn and roundrobin > use the same condition as below: > > fwlc_get_next_server(): > if (!s->maxconn || (!s->nbpend && s->s

Different check conditions for server selected from lb trees

2013-08-01 Thread Godbach
Hi Willy, Haproxy will check the number of concurrent sessions assigned to the server after being selected from lb trees. Both leastconn and roundrobin use the same condition as below: fwlc_get_next_server(): if (!s->maxconn || (!s->nbpend && s->served < srv_dynamic_maxconn(s))) { if (s !