My ORCID record: https://orcid.org/0000-0002-4379-4643
Contents:
%
% THE \simulan LOGO IS DEFINED HERE.
%
\def\simulan{{\rm s\kern-.06em\raise-.5ex\hbox{i}\kern-.1em\raise-.1ex
\hbox{m}\raise-.3ex\hbox{u}\kern-.10emL\kern-.1667em\lower-.6ex
\hbox{a}\kern-.10emn}}
%% the \PBeam Logo is defined here
\def\PBeam{{\sc\kern.15emP\kern-.9em\raise.125ex\hbox{$\leftarrow$}\sc\kern-.25emB\sc\kern-.1eme\kern-.1ema\kern-.1emm}}
is derived, and first measured results and experiences
with the implementation are reported.
A
BiBTeX-File, from my Dissertation.
und CoCheck, vorgestellt und
verglichen. Abschließend wird ein Ausblick auf neue
Funktionalitäten gegeben, die durch Integration mit interaktiven
Werkzeugen erreicht werden können.
-- Fehlertoleranz für
verteilte Anwendungen mittels Migration und Checkpointing.
system and its facility for creating global consistent
checkpoints of groups of communication process on networked Unix
systems, and present first experiences with our implementation.
system and focus on its facility for creating global
consistent checkpoints of groups of communicating processes on
networked Unix systems. We present first experiences with our
implementation.
. There we use a global virtual name space to achieve
location transparency for process migration and checkpointing /
rollback for distributed applications on clusters of Unix
workstations. First measurements have shown that the
maintenance of this global name space is critical for the
performance of the entire system.
The
system uses a global
virtual name space to provide migration and rollback
transparency in user space for distributed groups of processes
on workstations. Applications always use the same virtual
names for the operating system objects, independent of their
current real location. The system calls are interposed and
their parameters translated between the name spaces. Unlike
other migration mechanisms,
does not require the applications to be written
for a specific programming model or communication library.
The first approach to execute applications in the virtual name
space was to link the programs with a modified system
library. Now, in this paper we describe design and
implementation of a separate system call interposition process
that accesses the application via the debugging
interface. The main advantage of this approach is that it can
handle even unmodified (e.g. commercially bought)
application programs. We compare measured performance figures
with previous similar approaches and the modified system
library.
ISI Accession Number: WOS:000077612600023
2 citations in ISI Web of Science until August 2013
to also provide replication for
distributed applications. The approach to achieve these services
transparently for the application is the construction of a system-wide
virtual name space, which abstracts the running application processes
from the actual location and time of their execution. No changes to
the system kernel or the application code are required. Checkpointing
already is the common base for rollback and for migration, and now we
extend the migration to cloning to also achieve replication. With
application transparent checkpoint / rollback,
can only detect and treat crash faults. With replication
it now is also able to detect other faults by comparing the output of
the replica, even though it cannot know the meaning of the output
contents. The abstraction through the virtual name space is an
important prequisite to enable error detection through output
comparison on cluster systems. It ensures that no environment specific
information can yield differences in the replica outputs during
fault-free operation.