I guess you could look at a persistent memory mechanism for saving the
state of the application while it is migrated to the new node. If the
process has its data structures mirrored to disk, say, then you could
move both application and data to the new node and restart. I've been
looking at Coldstore (http://coldstore.sourceforge.net/), but don't
really have an application for it (yet). It works by mmapping data from
memory to disk -- you could adapt that mechanism to work with a DBMS as
well, if you do not want to be dependent on Coldstore itself.
Might be interesting, especially in conjunction with a MOSIX-like
Agilent Technologies Ltd. External: +44 131 331 6466
South Queensferry, EH30 9TG. Telnet: 313-3466
> Look at the Mosix project.
> > > I am currently working on an implementation of a Mobile Agent platform. The
> > > agents run in different processes on several host machines in a network.
> > > The agents and thus the processes have to be movable from one host to
> > > another for load balancing purposes.
> > > Does anybody know wether it is possible to capture the state of a running
> > > process, transfer it to another host and restarting it on the other machine
> > > in the same state as it left the first one
> > Look at the work being done by the Condor project at:
> > http://www.cs.wisc.edu/condor/
> > In addition, they wrote an article that you might try to find:
> > "Checkpointing and Migration of UNIX Processes in the Condor Distributed
> > Processing System" Dr Dobbs Journal, February 1995