You should ask this question on some HA mailing list. There are lots of HA solutions out there so google and you will find one that suits you. Search for DRBD, heartbeat, pacemaker for example or cluster HA with active/standby in your case. On Feb 7, 2012 5:22 PM, "Harsimranjit singh Kler" <simran...@gmail.com> wrote:
> > hi Denis > > thanks > > yes Apache Httpd do load balancing properly :-) only concern with fail > over support of httpd itself. > > eg. in my setup > Machine1 having : Apache httpd(2.2.17) and modjk (1.2.30)(Session > stickyness true and clustering not enabled) > Machine2:Tomcat6(worker1,worker2) > Machine3:Tomcat6(worker3,worker4) > Machine2:Tomcat6(worker5,worker6) > > So Machine1 is my single point of failure.So i was thinking one machine > with same configurations as Machine1 say MachineXX. > > MachineXX:Apache httpd(2.2.17) and modjk (1.2.30) > > so now if Machine1 goes down MachineXX should start taking new > requests and vica-versa. > > On Mon, Feb 6, 2012 at 5:30 PM, DENIS Laurent < > laurent.de...@mail.mobistar.be> wrote: > >> Apache supports load-balancing, you can put several in parallel without >> any problem J**** >> >> ** ** >> >> And it does a very nice job in load-balancing/failover for the backends >> through mod_proxy_balancer (though a health-check option at HTTP level >> would be welcome)**** >> >> ** ** >> >> The problem is more with the applications you put behind it. **** >> >> ** ** >> >> If you have several apache that forward to several application servers >> (be it PHP, Tomcat, Weblogic, Websphere, etc…) you need to make sure that: >> **** >> >> - one “client” always end on the same front-end apache server + that the >> queries are always forwarded to the same app server (using session id) ** >> ** >> >> - or that the app server are working in a cluster to synchronize their >> sessions**** >> >> ** ** >> >> If you can afford a hardware load-balancer, do so. But even there, you’ll >> have to setup several such boxes in parallel one day or another, with vrrp >> or hsrp or a similar protocol.**** >> >> ** ** >> >> You can also take a look at the SRV record for DNS ( >> http://en.wikipedia.org/wiki/SRV_record) and pray for the browser to >> support it.**** >> >> ** ** >> >> ** ** >> >> ** ** >> >> *From:* Harsimranjit singh Kler [mailto:simran...@gmail.com] >> *Sent:* Monday 6 February 2012 11:46 >> >> *To:* DENIS Laurent >> *Cc:* users@httpd.apache.org >> *Subject:* Re: [users@httpd] High availabilty through Apache httpd**** >> >> ** ** >> >> Thanks for details.**** >> >> **** >> >> One last question **** >> >> **** >> >> Why Apache not Support failover support which is basic for any load >> balancer setup ?**** >> >> **** >> >> Any plan of HA in future releases of httpd?**** >> >> On Mon, Feb 6, 2012 at 4:08 PM, DENIS Laurent < >> laurent.de...@mail.mobistar.be> wrote:**** >> >> Basically, you have one IP address that is used by two hosts, active one >> only one at a time. If one service fails, the other node take the IP thanks >> to keepalived.**** >> >> **** >> >> This works only if you’re on the same network segment.**** >> >> **** >> >> Google on “vrrp keepalived apache” and you’ll get this first link: >> http://www.cyberciti.biz/faq/rhel-centos-fedora-keepalived-lvs-cluster-configuration/ >> **** >> >> **** >> >> **** >> >> **** >> >> **** >> >> **** >> >> **** >> >> **** >> >> *From:* Harsimranjit singh Kler [mailto:simran...@gmail.com] >> *Sent:* Monday 6 February 2012 10:53 >> *To:* DENIS Laurent >> *Cc:* users@httpd.apache.org **** >> >> >> *Subject:* Re: [users@httpd] High availabilty through Apache httpd**** >> >> **** >> >> Intially i want failover setup only with two node**** >> >> **** >> >> can you explain little about vrrp + keepalived. else some reference >> link how i can achive it step by step(on linux setup only)**** >> >> ?**** >> >> On Mon, Feb 6, 2012 at 3:12 PM, DENIS Laurent < >> laurent.de...@mail.mobistar.be> wrote:**** >> >> If you just want failover on the head apache: use two nodes with vrrp + >> keepalived (if you’re on linux) to monitor your service.**** >> >> **** >> >> If you need load-balancing, then you should use two VRRP addresses with >> DNS round-robin. But you’ll stumble on client-server persistence problem if >> you don’t use tomcat clustering.**** >> >> **** >> >> **** >> >> *From:* Jaco Kroon [mailto:j...@uls.co.za] >> *Sent:* Monday 6 February 2012 10:24 >> *To:* users@httpd.apache.org >> *Cc:* Harsimranjit singh Kler >> *Subject:* Re: [users@httpd] High availabilty through Apache httpd**** >> >> **** >> >> Not that I'm aware of but someone else on the list may very well know >> something I don't. >> >> May I inquire as to why not? >> >> Kind Regards, >> Jaco >> >> On 06/02/12 11:17, Harsimranjit singh Kler wrote: **** >> >> >> Its is not possible for me to use "haproxy" in my setup. Is there >> alternate to use with Apache only?**** >> >> >> **** >> >> On Mon, Feb 6, 2012 at 2:43 PM, Jaco Kroon <j...@uls.co.za> wrote:**** >> >> Hi, >> >> Perhaps look at "haproxy" instead of apache. Run it on two or more >> machines with multiple IPs and have then distribute the load to your Tomcat >> worker nodes. >> >> Kind Regards, >> Jaco **** >> >> >> >> On 06/02/12 11:09, Harsimranjit singh Kler wrote:**** >> >> Hi >> How i can make apache httpd High Available(HA)?.If i want to achive with >> out hardware based HA. >> I have httpd 2.2.17 on one Phsical Node(IP xxx.xxx.xxx) and Six Tomcat >> worker on other 6 Phsical Node.Now if IP xxx.xxx.xxx goes down my >> application completly down.? >> regards >> Harsimran**** >> >> **** >> >> --------------------------------------------------------------------- >> The official User-To-User support forum of the Apache HTTP Server Project. >> See <URL:http://httpd.apache.org/userslist.html> for more info. >> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org >> " from the digest: users-digest-unsubscr...@httpd.apache.org >> For additional commands, e-mail: users-h...@httpd.apache.org**** >> >> **** >> >> **** >> >> *****DISCLAIMER********* >> >> **** >> >> This electronic transmission (and any attached document) is intended **** >> >> exclusively for the person or entity to whom it is addressed and may **** >> >> contain confidential and/or privileged material. **** >> >> Any disclosure, copying, distribution or other action based upon **** >> >> the information by persons or entities other than the intended recipient* >> *** >> >> is prohibited. If you receive this message in error, please contact the * >> *** >> >> sender and delete the material from any and all computers. **** >> >> Mobistar does not warrant a proper and complete transmission of this**** >> >> information, nor does it accept liability for any delays.**** >> >> **** >> >> *****END OF DISCLAIMER********* >> >> **** >> >> *****DISCLAIMER********* >> >> **** >> >> This electronic transmission (and any attached document) is intended **** >> >> exclusively for the person or entity to whom it is addressed and may **** >> >> contain confidential and/or privileged material. **** >> >> Any disclosure, copying, distribution or other action based upon **** >> >> the information by persons or entities other than the intended recipient* >> *** >> >> is prohibited. If you receive this message in error, please contact the * >> *** >> >> sender and delete the material from any and all computers. **** >> >> Mobistar does not warrant a proper and complete transmission of this**** >> >> information, nor does it accept liability for any delays.**** >> >> **** >> >> *****END OF DISCLAIMER********* >> >> ** ** >> >> *****DISCLAIMER***** >> >> >> >> This electronic transmission (and any attached document) is intended >> >> exclusively for the person or entity to whom it is addressed and may >> >> contain confidential and/or privileged material. >> >> Any disclosure, copying, distribution or other action based upon >> >> the information by persons or entities other than the intended recipient >> >> is prohibited. If you receive this message in error, please contact the >> >> sender and delete the material from any and all computers. >> >> Mobistar does not warrant a proper and complete transmission of this >> >> information, nor does it accept liability for any delays. >> >> >> >> *****END OF DISCLAIMER***** >> > >
