RE Re: available resource declaration language(s)

["David L. Nicol" <david@kasey.umkc.edu>]

> > 2) It should be a efficient method to send a task from the beginning to
> > the least loaded node  of the cluster. PVM have this, Mosix have not -in
> > Mosix the task can migrate after being launched, but its kernel part will
> > be executed on the launch node-.
> A cluster batch scheduler presumably could be a help here...

mosix is compatible with the farm-to-least-loaded-node mechanisms, not
exclusive of them; their web pages used to proudly proclaim that mosix would
supercharge a distribution mechanism for even greater throughput.

> For HA, automatic process migration in the kernel is a hinderance - not a
> help.  It makes it difficult to figure out what has failed, and to restart
> it on still-working nodes.  MOSIX's current implementation is what I'd call
> low-availability: For a 2-node cluster, having one node fail can cause all
> processes on both nodes to die.  This is not good for HA.

processes on a node that suddenly dies appear, in Mosix, to have been
given a kill -9 signal.  If your worker child processes can handle getting
kill-9ed without the whole house of cards collapsing, M. can become higher
availablity than the situation you describe.


-- 
                      David Nicol 816.235.1187 dnicol@cstp.umkc.edu
  He who says it's impossible shouldn't interrupt the one doing it.


Linux-cluster: generic cluster infrastructure for Linux
Archive:       http://mail.nl.linux.org/linux-cluster/