| View previous topic :: View next topic |
| Author |
Message |
Frank Cox
Joined: 13 Jun 2009 Posts: 17
|
Posted: Sun Jan 17, 2010 4:12 pm Post subject: Load balancing by IP address |
|
|
I have two computers, one webserver running Apache 2.2, and one Icecast server. The webserver has its own modem and IP address A, the Icecast server has two network cards in it on two separate modems, and IP addresses B and C.
The "clients" setting allows me to limit the overall number of connections, but I don't see any setting to limit the per-modem connections. Therefore, if I set "clients" to 100, in theory I could have all 100 streams on one modem while the other sits idle. This would not be a good thing.
Ideally I would like to somehow be able to present the users with a "click here to listen" webpage that will direct them to the least-busy modem on the Icecast server (or boots them if all modems are playing their maximum number of connections). |
|
| Back to top |
|
 |
jcr Modérateur français

Joined: 14 Apr 2006 Posts: 544 Location: France, Auvergne
|
|
| Back to top |
|
 |
Frank Cox
Joined: 13 Jun 2009 Posts: 17
|
Posted: Sun Jan 17, 2010 7:20 pm Post subject: |
|
|
Thank you once again! Round robin load balancing looks very interesting.
I can see a situation where, depending on the usage pattern, I could still end up with a majority of the clients streaming through one of the modems. I guess that this just means that I shouldn't try to push it to the limit when it comes to the total number of available connections.
Thanks a lot for the help! I have been puzzling over this issue for a week. |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Sun Jan 17, 2010 8:10 pm Post subject: |
|
|
You are going to be limited to new connections only but in theory you can use http 302 responses to redirect new connections to the other IP. The question then is what you use for doing the load balance. In the kh tree you can use auth url to redirect listeners to alternative addresses by returning a 200 OK response but by also returning a Location: header. This is to allow for people to load share between different servers not just different IPs.
karl. |
|
| Back to top |
|
 |
|