Re: [Clockwork-developers] Decision time

[Shawn D. <sd...@cf...>]

My preference is for a decentralized scheduler.  I think that the only real
downside is the load involved in getting a complete real-time view of the
entire schedule.  The advantages in removing the bottlenecks caused by a
dedicated server outweigh this.  Perhaps we could make a compromise, with
some number of distributed servers responsible for collecting scheduling
statuses from a subsets of servers.  These collector servers wouldn't do any
dispatching; they'd only collect job status broadcasts/unicasts from the
nodes in the subset.  Then the GUI management tool would only have to poll
these few collector servers to get the complete view.

Shawn


----- Original Message -----
From: "Joel Loudermilk" <jo...@lo...>
To: <clo...@li...>
Sent: Monday, March 11, 2002 8:47 PM
Subject: [Clockwork-developers] Decision time


> Shawn D. or Brian,
>
> Do you guys have an opinion on the centralized/decentralized question?
>
> I share Shawn M's feeling that we ought to choose a path and get on with
> the project.
>
> --
> Joel
>
> _______________________________________________
> Clockwork-developers mailing list
> Clo...@li...
> https://lists.sourceforge.net/lists/listinfo/clockwork-developers