[icecast-dev] Asymmetric load balancing

[Scott Manley]

Th redirect should of course include some info in the redirect URL 
regarding how many times it's been redirected - you don't want to get 
into a situation where users are bounced around indefinately.

Personally, I'd go a step further and collect performance data so that 
load balancing can make better decisions for redirects. No sense in 
redirecting a local connection to a remote site.

<p><p>> Round robin DNS isn't really appropriate as you noticed.  Something will
> have to be done among the icecast servers themselves, and what is coming
> to my mind really quickly is some kind of new config option to specify a
> list of mirror servers.
> 
> If the client limits are hit on the server, it sends back an HTTP
> redirect with the location of a random mirror (not itself).  This should
> be transparent to clients and acheive the affect you want.  You could
> also combine with with round robin DNS to spread people over the servers
> initially.
> 
> Seems fairly elegant.  Probably you want this configurable on a mount
> level not a global server level, but it shouldn't be too hard to
> implemenet.  Just a config file addition plus some extra logic in the
> main connect loop, similar to what happens on a 404.
> 
> jack.
> --- >8 ----
> List archives:  http://www.xiph.org/archives/
> icecast project homepage: http://www.icecast.org/
> To unsubscribe from this list, send a message to 'icecast-dev-request at xiph.org'
> containing only the word 'unsubscribe' in the body.  No subject is needed.
> Unsubscribe messages sent to the list will be ignored/filtered.
> 

--- >8 ----
List archives:  http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to 'icecast-dev-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.