• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Apache load balancing

 
Rancher
Posts: 13459
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
We run about 100 domains on two apache servers (two physical machines, one Apache process each)
Each domain is configured to go explicitly to one server or the other and that set up is fine, except when there is a hardware issue.
If we need to direct all traffic to one server, we need to do it via DNS and that takes a long time to propagate.

We're in the process of converting the two machines to Virtual Machines, but I would still like a bit of flexibility in terms of Apache configuration.
NOTE: we don't want round robin between servers, requests for a domain should go to a single machine unless asked to change.

I was thinking about a hardware solution, but I'm not sure what they cost and whether they will do what we want.
My preferred solution may be to set up a thin VM that provides a single front end for all requests and directs (per virtual domain name) to an internal apache server.

or am I missing something?
 
reply
    Bookmark Topic Watch Topic
  • New Topic