Hi,
On Sat, Dec 5, 2009 at 10:24 AM, Andrew wrote:
> It would seem to be logical to me for liquidsoap to make sure that it is
> sending metadata to the origin server that it connected to so that relays can
> retrieve the metadata as well.
That would seem logical to me as well, and I don't see
I would argue that randomized DNS with relaying is a very good solution for
load balancing live audio streams. It has an advantage over a single master
server in that there is no single point of failure.
It would seem to be logical to me for liquidsoap to make sure that it is
sending metadata t
It seems a quick workaround to solve your problems, but I don't think
it is the correct solution for the problem. You just get what you've
asked for: you have setup load balancing over several IPs and now the
client connects to different servers. If the servers cannot handle
this, it is not the fau
The "root" icecast server doesn't need to live on the same box. You could
still deploy it to a public location, and always push to that icecast
server. The cluster members can pull from that root server, then you don't
have to keep track of IP's.
DJ box ---> root icecast server <--- cluster member
Unfortunately that won't work in my case, as the encoding computer running
liquidsoap is at a different location from the servers that listeners listen
to.
Running a local icecast isn't feasible as a public IP is not an option at the
encoder site, and as I understand it, Icecast can't do push-
I may not understand your scenario totally, but would it make sense to have
a local icecast server that Liquidsoap sources? Then each of the other
icecast servers in the cluster, which I'm assuming are for listening, all
pull from that one mount point on the Liquidsoap box.
On Tue, Dec 1, 2009 at
Hi,
It makes a lot of sense, I think that it'd be a good idea. Please file
a ticket on our trac (http://savonet.rastageeks.org/) and we'll take
care of that quickly I think. However, this would only apply to the
SVN version. It is still unstable, although that shouldn't last too
long. I'm not sure
Hi there,
For load balancing and redundancy, I have several icecast servers in place. I
have setup a DNS entry called icecast.domain.com which randomly points to
different servers in the cluster and use relaying on-demand to make sure that
each server has the ability to serve the stream.
I hav
