Author |
|
Qmpeltaty
Joined: 06 Feb 2008 Posts: 182 Location: Poland
|
Posted: Tue 20 May '14 14:20 Post subject: Apache farm, cluster |
|
|
I wonder if there is any well known, good practice for clustering, merging more than one Apache instance ?
Assumming that webpage is very popular, concurrent connections amount is overwhelming one Apache instance, there is no more to squizee from Apache configuration, no more code of application to improve - what would you do ? |
|
Back to top |
|
Qmpeltaty
Joined: 06 Feb 2008 Posts: 182 Location: Poland
|
Posted: Thu 22 May '14 11:04 Post subject: |
|
|
Anybody ? |
|
Back to top |
|
Steffen Moderator
Joined: 15 Oct 2005 Posts: 3092 Location: Hilversum, NL, EU
|
|
Back to top |
|
Qmpeltaty
Joined: 06 Feb 2008 Posts: 182 Location: Poland
|
Posted: Fri 23 May '14 12:58 Post subject: |
|
|
Steffen wrote: | No hurry, maybe the weather keeps ppl away |
You could be right Steffen - it's nice time to get some Sun
Steffen wrote: |
Did you have a look at mod_proxy_balancer.. |
This is not exactly what i need. My Apache instances are loadalancers for JBoss application servers (in some scenarios +10 nodes of JBoss behind Apache) - and this is what you wrote about (i use mod_jk instead of mod_proxy).
What i need is to use multiple Apache instance in front of multiple JBoss nodes . I'm looking for solution like Ucarp, Ultramonkey etc. - but on Windows. |
|
Back to top |
|
James Blond Moderator
Joined: 19 Jan 2006 Posts: 7371 Location: Germany, Next to Hamburg
|
Posted: Mon 26 May '14 10:44 Post subject: |
|
|
I was at vacation
I think you can use mod_heartbeat and mod_watchdog. And maybe mod_lbmethod_heartbeat.
Before Apache 2.4 I used several public IP adresses and a round robin loadbalancer. |
|
Back to top |
|
Qmpeltaty
Joined: 06 Feb 2008 Posts: 182 Location: Poland
|
Posted: Mon 26 May '14 11:27 Post subject: |
|
|
James Blond wrote: |
Before Apache 2.4 I used several public IP adresses and a round robin loadbalancer. |
Roung robin loadbalancer is quite wide - on what level you have it (DNS, http request)? |
|
Back to top |
|
James Blond Moderator
Joined: 19 Jan 2006 Posts: 7371 Location: Germany, Next to Hamburg
|
Posted: Mon 26 May '14 12:10 Post subject: |
|
|
I used DNS based round robin. It has the huge disadvantage if a server fails and the client caches the IP it will fail some times. Sure the balancer knows which server is online, but client caching is problem.
That is why I look into mod heartbeat, but I haven'#t found a good tutorial yet.
In an ideal world, I would have 2 apache servers as loadbalancer with hotstandby failover. Behind those two a bunch of apache reverse proxies and behind that the APP servers. Currently the hotstandby is done by hand |
|
Back to top |
|
Qmpeltaty
Joined: 06 Feb 2008 Posts: 182 Location: Poland
|
Posted: Tue 27 May '14 9:31 Post subject: |
|
|
Ush, manual hotstandby sucks For me it's more important to get additional threads for handling more incoming traffic - failover is less imporatant but would also be nice to get this functionality. |
|
Back to top |
|
James Blond Moderator
Joined: 19 Jan 2006 Posts: 7371 Location: Germany, Next to Hamburg
|
Posted: Tue 27 May '14 16:57 Post subject: |
|
|
Well back to the original question. I would set an apache loadbalancer in front of the bunch of apache reverse proxies.
However having DNS based round robin with some external IPs can handle more incoming traffic. |
|
Back to top |
|
PipoDeClown
Joined: 20 Dec 2005 Posts: 77
|
Posted: Tue 27 May '14 23:46 Post subject: |
|
|
Windows has Network load balancing. Instead of roundrobin dns this can do HA and session affinity. Behind that throw some caching reverse proxies that point to your backend.
machine 1:(NLB-->SSL Termination-->Load balancer)-->machine 2:(Reverse proxy)-->Backend
Aswell add mod_security with all rules enabled to the reverse proxies just for fun |
|
Back to top |
|
James Blond Moderator
Joined: 19 Jan 2006 Posts: 7371 Location: Germany, Next to Hamburg
|
Posted: Wed 28 May '14 11:01 Post subject: |
|
|
A much harder to implement solution is to use a CDN for static files via subdomain. e.g. static.example.com
That makes the deployment harder and the HTML code needs to be changed. |
|
Back to top |
|