On Mon, Aug 4, 2014 at 6:15 AM, Sukrit Khera <[email protected]> wrote: > We are planning to setup proxy service using HaProxy. We realized that when > we send multiple reload signals at same time, haproxy process count > increases and the old process do not die. > > If we serialize the reload requests( i.e. execute one after other), we do > not see the leak. > > Note : This happens even when there is not traffic to the site and the old > process never die. > > sukrit@sukrit-dev:~$ haproxy -v > HA-Proxy version 1.5.3 2014/07/25 > > Linux (Ubuntu Trusty 14.04) : 3.13.0-32-generic > > Test Script : > service haproxy reload & > service haproxy reload & > > Use Case: We are providing proxy as a service to our internal apps to do a > blue green deploy. Once new app comes up, we do a reload. SInce we have > multiple workers running which processes the deployment request, at times we > might have 2 proxy requests being served at same time. > > I was wondering if that is intended behavior and our script should handle > the serialization of request or if it is a bug. > > Thanks and Regards > Sukrit Khera
Hi Sukrit, This behavior occurs by design. Can you share with us your configuration? Old processes remains active as long as it has an active connection. A connection could remain active because there is data exchanged on it or because you set up very long time outs. Could you share with us your configuration (don't forget to anonymize it) Baptiste
