Hi Amol,
I belive that you will be wanting to use rules in your front end something
like this:
acl rule1 path_beg -i mon
use_backend backend1 if rule1
acl rule2 path_beg -i tue
use_backend backend2 if rule2
cheers
john
On 17 February 2011 21:11, Amol wrote
After a bit more experimenting - I have found that number of ports which
haproxy can listen on is set by the number of file handles per process.
On linux systems this is set at 1024 by default, hence the limit 1024,
however this can be changed by editing :
/etc/security/limits.conf
where it is p
sorry typo,
meant to read:
stick on src unless no_persist_backup
On 6 December 2010 20:23, John Carter wrote:
> Hi Everybody,
>
> I'm tying to make backup servers not enter the persistence table, but as
> yet , I have had no success
>
> I was thinking that I co
Hi Everybody,
I'm tying to make backup servers not enter the persistence table, but as yet
, I have had no success
I was thinking that I could stop a server being entered in to the persistent
table like this:
r...@vm11:/etc/haproxy# cat haproxy.cfg
global
#uid 99
#gid 99
daemon
Hi,
I have found that if I use Source IP persistence with both backend servers
and a backup server. If the backend servers go down then I will be directed
to the backup server, as it should be.
However, my persistence is now change to be on the backup server and if the
backend come back online, m
5 matches
Mail list logo