Re: Clusterwide pids

[Patrick Spinler <spinler.patrick@mayo.edu>]

"Albert D. Cahalan" wrote:
> 
> It is better to pass out chunks of PID space or
> lists of free PIDs. When a node uses half of its allocation, it can
> send a request for more PID space.

(snip)

> Assign node number via the kernel command line, or assign it
> when the cluster is joined.
> 

This scheme is quite straightforward, which is good. But in my limited
understanding it seems to place a cluster architechure in one of two
possibly difficult to resolve scenarios:

a) cluster_id's and pid ranges are hardcoded at boot time
   -) potentially difficult to administer large or highly dynamic
cluster(s)

b) node has to join cluster and request pid range's & cluster id before
starting any processes
   -) all key cluster membership management & control must be kernel
level
      (this may be necessary anyway)
   -) still have to assume certain processes & pid's are local node
only, 
      e.g. init is assumed to be pid 0 in many places, correct ?

How might you address these problems ?  Have I misunderstood ?

-- Pat

-- 
      This message does not represent the policies or positions
	     of the Mayo Foundation or its subsidiaries.
  Patrick Spinler			email:	Spinler.Patrick@Mayo.EDU
  Mayo Foundation			phone:	507/284-9485

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