LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 01-22-2006, 07:24 AM   #1
Harlin
Member
 
Registered: Dec 2004
Location: Atlanta, GA U.S.
Distribution: I play with them all :-)
Posts: 316

Rep: Reputation: 38
Setting Up Apache Round Robin Servers


Looking for opinions here (anything is fine).

At work we are considering setting up a page where our customers can download Podcasts. These will be simple mp3 files. At this point we are almost certain that we can expect about 300-400 simultaneous connections at certain times in the day for this. As such, we are wanting to use two frontend servers that will use Heartbeat to ensure that at least one of these two servers will be up. Next, the frontend server that is up will direct round-robin style to three different web servers we will have running (in addition to the first two).

Has anyone had any experience doing round-robin with Apache? I've looked at a few docs and this seems simple. My concern is mainly performance. I am wondering if our amount of hardware will be able to handle a 300-400 simultaneous connection load. All five of our servers will have dual processors (2.8 GHz at least) with about 8GB of memory each and use either RHEL 4 or Suse Enterprise 9. Any comments, suggestions or questions would be welcome about this. Also, if for some reason our hardware may seem to be overkill, what would some of you suggest as minimum hardware configs to get this done?

Thanks,

Harlin
 
Old 02-02-2006, 08:18 PM   #2
stress_junkie
Senior Member
 
Registered: Dec 2005
Location: Massachusetts, USA
Distribution: Ubuntu 10.04 and CentOS 5.5
Posts: 3,873

Rep: Reputation: 335Reputation: 335Reputation: 335Reputation: 335
I've only read about this. I have heard that if you set up your DNS server to have multiple definitions of the same name with different IPs then it will serve the IPs in round robin style. That means that you don't need your front end server as you describe in your post. This does not take your failover into account. If one of the two servers was down then half of the connect requests would receive 'node not reachable'.

How to overcome this? Again, just a theory. Both web servers have two virtual NICs. Each virtual NIC has the address of the web server addresses. When the heartbeat tells each node that the other is running then only the virutal NIC with the node's address is active. If heartbeat says that the other node is down then the virtual NIC with the address of the other web server is activated.

I've been meaning to try this. If you do then please let me know how it worked out.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
dns round-robin tzkolinux Linux - Networking 1 12-27-2004 03:49 AM
Setting Up DNS Round Robin? Longhair Linux - Networking 0 05-26-2003 01:34 AM
Setting Up DNS Round Robin Longhair Linux - Newbie 0 05-25-2003 12:09 PM
round robin for servers deepagodkhindi Programming 5 05-11-2003 05:50 AM
Round Robin DNS Lucsi Linux - Software 1 07-18-2002 04:17 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 11:39 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration