Tait Clarridge wrote on 02/05/2015 09:55 PM:
[CUT]
Just to check.. if I set nbproc to f.ex. 4 - then I understand I need to
define 4xstats.. and when I visit the webinterface.. I'll actually only
get stats from one of the 4 processes..
But we have ADMIN enabled for stats - so we can disable backend servers
etc.. will we have to do that for each of the 4 stats "editions" -
before it's actually active or is that state shared among them all?
Yes, you have to do all our admin operations on each webinterface.
Cheers,
Pavlos
You can also write a small application to take the admin requests and
send them to each haproxy process' web interface, or you can set the
backend server health check to something you can dynamically change to
start failing and bring the server down "gracefully" that way.
So instead of actually using the nice ADMIN mode that someone authored..
I have to write my own, if I want to scale haproxy?
:(
I believe varnish solves this scaling by using threads instead - and
hence varnishadm/stats works no matter how many threads one has.
Using a process/pre-forker model instead could work just as well, if one
used shared-memory or some other form of IPC..
I realize it's obviously not an itch that's scratching for anyone
currently.. but is there already a feature request somewhere on this, or
can I file one? :)
--
Regards,
Klavs Klavsen, GSEC - [email protected] - http://www.vsen.dk - Tlf. 61281200
"Those who do not understand Unix are condemned to reinvent it, poorly."
--Henry Spencer
