Re: [SSI] process migration
Brought to you by:
brucewalker,
rogertsang
From: Aneesh K. K.V <ane...@di...> - 2002-11-14 05:47:32
|
On Wed, 2002-11-13 at 23:57, Bruce Walker wrote: > snip > > > That means a.out ran on node1 even after rebooting node2. So for a > > simple application like above it will work. > > > snip > > > > > What kind of dependencies? Aneesh talked > > > about some pseudo processes. > > It is not me how said about pseudo process. I was replying to a mail from linux kernel mailing list.Prasad was talking about pseudo process which he was planning in his implementation . > As I responded to another message, there is no pseudo process > on the process's creation node. The creation node does keep track > of the existence of the process and location where it is running, for > two reasons - one, so it doesn't reuse the pid; second so it can > help other processes locate the process in order to send signals,etc. > (all done transparently in the kernel, of course). If the > process creation node (called the origin node in the code) goes away, however, > another node (surrogate origin node) transparently takes over the > tracking of the process. Thus the loss of the creation node is > transparent. Note that when the creation node rejoins the cluster, it > resumes the tracking of old processes, for lots of good reasons. > How do i get to know about the surrogate node. From the PID i can find the creation node ( right ? ). But if the creation node goes down which subsystem gives me information of surrogate origin node. Is this the master node ? In that case what happens if master node also went down ? Does this information is build again by asking all the nodes ? Any hint on code part ? ( Is it VPROC I should be looking at ) NOTE regarding DLM, the lock manager documentation can be found at . http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/opendlm/opendlm/docs/lockmgr.txt?rev=HEAD&content-type=text/plain -aneesh |