Queue Cur is a gauge and so not representative of historical values. Queue Max of zero is telling though.
In addition to queue timeout, there are other ways haproxy can synthesize an http response on behalf of the backend server. Check for connection errors. On Wed, Sep 7, 2016 at 12:15 PM Dmitry Sivachenko <trtrmi...@gmail.com> wrote: > > > On 07 Sep 2016, at 21:10, PiBa-NL <piba.nl....@gmail.com> wrote: > > > > Hi Dmitry, > > Op 7-9-2016 om 15:54 schreef Dmitry Sivachenko: > >> Hello, > >> > >> (sorry for reposting, but I do not see my e-mail in ML archive, so I > assume it was blocked due to screenshots in attachments. I replace them > with links now). > >> > >> I am using haproxy-1.6.9. > >> > >> In web stats interface, I mouse-over backend's Total Sessions counter > (1728 in my case), and I see HTTP 5xx responses=46 > >> (see screenshot: https://people.freebsd.org/~demon/scr1.png) > >> > >> Then I mouse-over each server's Total sessions counter and none has > positive number of HTTP 5xx responses (see second screenshot: > https://people.freebsd.org/~demon/scr2.png). > >> > >> Is it a bug or I misunderstand these counters? > >> > >> Thanks! > > > > In a case if all servers are down (or very busy). > > > > A request could be queued and then timeout, so haproxy itself will > return for example a 503, while none of the servers ever returned anything > for that specific request. > > > > I'm not saying this is the exact scenario you see, but it might explain > it.. > > > > > In "Queue" section I have all zeroes in Cur and Max. > > >
