when haproxy will invoke hijacker?
Hello: Now I am adding a extra function to haproxy, but when I debug, I find at expiration, haproxy exportes core dump on invoking hijacker, but I could not find when the buffer-flags ORING BF_HIJACKER, I am really confused. and in 1.4.2 version hijacker are always null? how can I set this function? could I remove all the code in -- Mr. XiaoxinLin - 林晓鑫(分机：5529)xiao...@staff.sina.com.cn 研发中心 - 基础架构部 -基础技术 RD Center
Re: Rollover Backups
Laurie Young wrote: Hi everyone Hi Laurie This should all be doable It it possible to provide a list (2 is enough, more would be better) of backup servers, which behave in the following way * All requests go to the main server * This is done by specifying all additional servers as backup when configuring them in the backend * If the server goes down, all requests go to the backup * this is handled by setting the option above. * if the main server goes up - requests continue going to the backup (until manual intervention) * This is done by specifying a cookie on your backup server - the requests will then continue to be handled by that server until the session expires (or the server goes down) /optionally/ * if the backup server goes down, all requests go to backup 2 * If you have multiple backup servers make sure you do not specify option allbackups as this will send traffic to all of your backup servers, rather than progressing through them. Chris -- Dr Laurie Young Scrum Master New Bamboo Follow me on twitter: @wildfalcon Follow us on twitter: @newbamboo Creating fresh, flexible and fast-growing web applications is our passion. 3rd Floor, Gensurco House, 46A Rosebery Avenue, London, EC1R 4RP http://www.new-bamboo.co.uk
Re: Rollover Backups
Thanks for the response chris * if the main server goes up - requests continue going to the backup (until manual intervention) * This is done by specifying a cookie on your backup server - the requests will then continue to be handled by that server until the session expires (or the server goes down) Unfortunately the servers here are not web servers, so setting a cooke is not an option. I also need new requests to go to the backup - not just sessions already in play. It's an instance of Redis, (a key value store). The main server would be the master, with the backup being the slave. If the master goes down and write operations get sent to the slave, we cannot send ANY requests to the master till we have been able to re-sync them (which is a manual operation) -- Dr Laurie Young Scrum Master New Bamboo Follow me on twitter: @wildfalcon Follow us on twitter: @newbamboo Creating fresh, flexible and fast-growing web applications is our passion. 3rd Floor, Gensurco House, 46A Rosebery Avenue, London, EC1R 4RP http://www.new-bamboo.co.uk
Re: failover with HAproxy
On Wed, May 12, 2010 at 2:50 PM, Bob Sauvage bob.sauv...@gmx.fr wrote: Hello people ! Is it possible to make a simple failover mechanism with Haproxy ? I don't want load balancing at this moment. Just a director who checks my two webservers. If my webserver 1 is down, the director redirects the paquet to the webserver2. Thanks a lot ! ;) Hi Bob, I read that the combination of HaProxy and KeepAlived works pretty well. KeepAlived will do what you are trying to achieve. Sam
Re: failover with HAproxy
Hi Bob, I guess you are talking about the backup option? Check out http://haproxy.1wt.eu/download/1.4/doc/configuration.txt in section 5: backup When backup is present on a server line, the server is only used in load balancing when all other non-backup servers are unavailable. Requests coming with a persistence cookie referencing the server will always be served though. By default, only the first operational backup server is used, unless the allbackups option is set in the backend. See also the allbackups option. So you basically configure two server in your listen/backend section. The backup server will have to contain the backup keyword. Best, Michael Am 12.05.2010 20:50, schrieb Bob Sauvage: Hello people ! Is it possible to make a simple failover mechanism with Haproxy ? I don't want load balancing at this moment. Just a director who checks my two webservers. If my webserver 1 is down, the director redirects the paquet to the webserver2. Thanks a lot ! ;)
Re: Rollover Backups
Hmm turn off autostart of your master server so it cannot accidentally go up ? U have to resync it manually anyway Dnia 2010-05-13, czw o godzinie 12:36 +0100, Laurie Young pisze: Thanks for the response chris * if the main server goes up - requests continue going to the backup (until manual intervention) * This is done by specifying a cookie on your backup server - the requests will then continue to be handled by that server until the session expires (or the server goes down) Unfortunately the servers here are not web servers, so setting a cooke is not an option. I also need new requests to go to the backup - not just sessions already in play. It's an instance of Redis, (a key value store). The main server would be the master, with the backup being the slave. If the master goes down and write operations get sent to the slave, we cannot send ANY requests to the master till we have been able to re-sync them (which is a manual operation) -- Dr Laurie Young Scrum Master New Bamboo Follow me on twitter: @wildfalcon Follow us on twitter: @newbamboo Creating fresh, flexible and fast-growing web applications is our passion. 3rd Floor, Gensurco House, 46A Rosebery Avenue, London, EC1R 4RP http://www.new-bamboo.co.uk -- Mariusz Gronczewski (XANi) xani...@gmail.com GnuPG: 0xEA8ACE64 http://devrandom.pl signature.asc Description: To jest część wiadomości podpisana cyfrowo
