Re: Haproxy stats bug with nbproc > 1

2013-10-19 Thread Willy Tarreau
Hi Boris,

On Thu, Oct 17, 2013 at 11:14:38PM -0500, Boris wrote:
> Hi,
> 
> With haproxy 1.4.22 and you enable the stats page (to 
> monitor/enable/disable servers), it works great with nbproc set to 1(by 
> default). When you enable nbproc > 1, Each time you refresh the page, a 
> different page is shown depending on the thread. This is really 
> annoying. (and I would almost call it a bug) When you try to 
> enable/disable servers through the web gui, you have to refresh multiple 
> times (so it can cycle through every thread) to actually enable/disable 
> a server. Will this be fixed in Haproxy 1.5? (or current in Git?) Thanks.

It is a well known limitation which is even explained in the doc :

  Note : Consider not using this feature in multi-process mode (nbproc > 1)
 unless you know what you do : memory is not shared between the
 processes, which can result in random behaviours.

Yes for sure this is annoying and we would all like to see this change.
Doing it represents a significant amount of work and will likely affect
general performance.

For now the best solution you can use is to have one stats page per
process (eg: using a different IP or port). Something like this for
example :

   listen stats-proc1
   bind 127.0.0.1:8080
   bind-process 1
   stats uri /

   listen stats-proc2
   bind 127.0.0.2:8080
   bind-process 2
   stats uri /

   listen stats-proc3
   bind 127.0.0.3:8080
   bind-process 3
   stats uri /

etc...

That said, you're saying that you're running on 1.4. So it's not
even for SSL that you're running with nbproc > 1. Do you have a
very good reason for this ? 

Hoping this helps,
Willy




Haproxy stats bug with nbproc > 1

2013-10-17 Thread Boris

Hi,

With haproxy 1.4.22 and you enable the stats page (to 
monitor/enable/disable servers), it works great with nbproc set to 1(by 
default). When you enable nbproc > 1, Each time you refresh the page, a 
different page is shown depending on the thread. This is really 
annoying. (and I would almost call it a bug) When you try to 
enable/disable servers through the web gui, you have to refresh multiple 
times (so it can cycle through every thread) to actually enable/disable 
a server. Will this be fixed in Haproxy 1.5? (or current in Git?) Thanks.



--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.