Hi Thomas, thanks for the suggestion! I'm hoping for a built-in solution
with the existing stats data. Would scur=0 on the server stats be an
accurate test? I'm dubious because I tested disabling http-server-close and
the active server in question still shows scur of 0 most of the time; the
requests are for a web service that typically responds in <100ms, but it's
still handling 500-1000 requests per minute, so I would expect to see more
sessions.

Also, I just pulled stats for the server and scur for the frontend is 73
but total for all the backends is 1. Why is that if http-keep-alive is set?

On Wed, Oct 29, 2014 at 6:41 PM, Thomas Heil <[email protected]>
wrote:

>  Hi,
>
> On 29.10.2014 23:09, Tom Keyser wrote:
>
> Along this same vein...
>
>  We're using HAProxy to execute seamless mid-day deployments of
> high-volume critical services. The http-server-close option is set. The
> backend of an example service is like so:
>
>     server svr2 192.168.1.19:80 check
>   server svr2_staging 192.168.1.19:8080 disabled check
>
>  Our deployment system is configured to copy new binaries to the
> svr2_staging server, then use the stats socket to change the svr2_staging
> state to "ready" and the svr2 state to "drain". My question is how can I be
> sure all existing sessions to the svr2 server are closed before I start
> copying binaries to it?
>
>  One idea that comes into my mind is to use a stick table and and poll as
> long as there are server_id that belongs to a server
> that should be upgraded.
> The worse case would be polling as long as the expire timeout for the
> stick-table.
>
>
>  On Wed, Oct 29, 2014 at 12:06 PM, Baptiste <[email protected]> wrote:
>
>>  On Fri, Oct 24, 2014 at 4:37 PM, Ian Cooke <[email protected]> wrote:
>> > Hi,
>> >
>> > Can haproxy change the backend for an existing session?  I have a
>> stateless
>> > client/server and I thought 'redispatch' did what I want but it seems
>> that's
>> > only for the initial connection.  What I'd like is for a client that's
>> > already been connected to maintain the frontend's connection but change
>> the
>> > session's backend server if the one it's connected to goes down.
>> >
>> > Thanks,
>> > Ian
>>
>>  Hi,
>>
>> maybe http-server-close is the option you're looking for.
>>
>> Baptiste
>>
>>
>
>
>  --
>
>   cheers,
> thomas
>
>


--

Reply via email to