Re: Clusterwide pids

[Chris Wright <chris@wirex.com>]

* Albert D. Cahalan (acahalan@cs.uml.edu) wrote:
> Chris Wright writes:
> > * Albert D. Cahalan (acahalan@cs.uml.edu) wrote:
> >> 
> >> 1. boot the single node without joining the cluster
> >> 2. fix the node
> >> 3. reboot to join the cluster
> > 
> > sounds like a windows soultion ;-)  seriously though, if you can boot
> > and run processes that are local only (no cluster yet, as you haven't
> > been able to join for whatever reason), how does this cause problems when
> > you join the cluster?
> 
> Conflicting PIDs are bad.

of course.

> 
> Being tied to a node is fine. Just do it with a unique PID.
> On an SMP system, one may support the ability to lock a process
> onto a processor. This doesn't mean you should allow that PID
> to be used for a different process on a different CPU.

sorry, implicit in my thinking was a node id as part of the pid.  a node
id of something like 0 being akin to local only.  a non-zero node id
being akin to a cluster process.  (analogous to 127.0.0.1 and the ip
addr of your admin interface)

-chris

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