From: Larry Bouthillier <[EMAIL PROTECTED]>
Subject: Re: Monitor port
I've done a version of this, slightly differently. I open (and close) a Java
socket connection to port 7070 on the RealServer every sixty seconds. If the
RealServer dies, this connection will fail and my program sounds an alarm.
Interestingly, the only server death I've experienced on our Solaris production
systems has been due to hardware failure. I'm not sure what it would do if I'm
out of streams, I haven't had that happen yet.
As for the load balancing, I simply generate ram files on the fly that send
requests to one of the servers (which contains the requested video) at random,
without monitoring current server load. This statistical approach works well.
I've never seen the load go off balance by more than 60-40, and that's just
random effects of how long people happen to stay connected once they are
watching.
Of course, it's then easy to connect the two aforementioned functions -- if a
server dies for any reason as detected by the first program, the second one
stops referring requests to it.
Larry
RealForum wrote:
> From: Tim McSweeney <[EMAIL PROTECTED]>
> Subject: Monitor port
>
> Is the protocol of monitor port documented somewhere?
>
> I am interested in writing my own utilities that connects to it to query
> the state of the server.
>
> Ultimatley I would like to write two utilities, one to notify me when
> things go wrong (the server crashing, running out of streams, etc)
>
> The second would monitor several servers and do primitive load balancing by
> generating ram files on the fly to serve the content off the different
> servers based on how busy they are.
>
> Of course if there is already a way to do either of these tasks I would be
> interested in that as well.
>
> Cheers
> Tim
