Preemptable remote execution facilities for the V-system

Theimer, Marvin; Lantz, Keith A.; Cheriton, David R.

doi:10.1145/323647.323629

Cited by 196 publications

(78 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Process-level migration has been studied extensively in the past [32], [37], [46], [26], [4], [11], [15]. In the context of HPC, many MPI implementations have been retrofitted with or design for FT, ranging from automatic methods (checkpoint-based or log-based) [44], [41], [5] to nonautomated approaches [3], [17].…”

Section: Related Workmentioning

confidence: 99%

Proactive process-level live migration and back migration in HPC environments

Wang

Mueller

Engelmann

et al. 2012

Journal of Parallel and Distributed Computing

View full text Add to dashboard Cite

As the number of nodes in high-performance computing environments keeps increasing, faults are becoming common place. Reactive fault tolerance (FT) often does not scale due to massive I/O requirements and relies on manual job resubmission.This work complements reactive with proactive FT at the process level. Through health monitoring, a subset of node failures can be anticipated when one's health deteriorates. A novel process-level live migration mechanism supports continued execution of applications during much of processes migration. This scheme is integrated into an MPI execution environment to transparently sustain health-inflicted node failures, which eradicates the need to restart and requeue MPI jobs. Experiments indicate that 1-6.5 seconds of prior warning are required to successfully trigger live process migration while similar operating system virtualization mechanisms require 13-24 seconds. This self-healing approach complements reactive FT by nearly cutting the number of checkpoints in half when 70% of the faults are handled proactively.

show abstract

Section: Related Workmentioning

confidence: 99%

Proactive process-level live migration and back migration in HPC environments

Wang

Mueller

Engelmann

et al. 2012

Journal of Parallel and Distributed Computing

View full text Add to dashboard Cite

show abstract

“…When searching for an agent, the location object is first looked up at a local name server. If not found, it is looked When locating agents, different location schemes are used, similarly to those used in distributed operating systems, such as Charlotte [3], V kernel [31], Sprite [12] and Mach [23]. The MOA system supports: a) updating the home after agent moves, b) registering at a predefined name server, c) searching based on predefined itinerary and d) forwarding based on the trails left after migration (see Figure 9).…”

Section: Naming and Locatingmentioning

confidence: 99%

“…Process migration in the Sprite operating system supported the notion of a home node [12]. In the V Kernel process migration [31], migrating processes are located by searching them. Emerald supports fine grain mobility on a small scale network, addressing mobility at the language level [19].…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Mobile Objects and Agents (MOA)

Milojicic

LaForge²,

Chauhan³

1998

Distrib. Syst. Engng.

View full text Add to dashboard Cite

This paper describes the design and implementation of the Mobile Objects and Agents (MOA) project at the Open Group Research Institute. MOA was designed to support migration, communication and control of agents. It was implemented on top of the Java Virtual Machine, without any modifications to it. The initial project goals were to support communication across agent migration, as a means for collaborative work; and to provide extensive resource control, as a basic support for countering denial of service attacks. In the course of the project we added two further goals: compliance with the Java Beans component model which provides for additional configurability and customization of agent system and agent applications; and interoperability which allows cooperation with other agent systems.This paper analyzes the architecture of MOA, in particular the support for mobility, naming and locating, communication, and resource management. Object and component models of MOA are discussed and some implementation details described. We summarize the lessons learned while developing and implementing MOA and compare it to related work. IntroductionMobility has always attracted researchers in computer science. This interest spans from general observations, such as "if it weren't for mobility, we would still be trees" [10], and the analogies with the real world "migrating birds and nomadic tribes moving due to the lack of resources", to purely technical reasons, such as improving locality of reference and difference between local and remote semantics.One of the first incarnations of software mobile entities. is worms [30], which could spread across nodes and arbitrarily clone. Unrestricted implementations of worms and viruses have received negative connotations, due to security breaches and denial of service attacks [13].The next generation of mobile entities, known as process migration, were implemented at the operating sysThis work was supported in part by the Advanced Research Projects Agency and the Rome Laboratory of the Air Force Materiel Command. tem (OS) level. There were many implementations of process and object migration [3,12,19,31], but none has achieved wide acceptance. Due to inherent complexity, it was hard to introduce process migration without impacting the stability and robustness of the underlying OS.Mobile objects and agents have attracted significant attention recently. In addition to mobile code (such as applets), agents consist of data and non-transient system state that can travel between the nodes in a distributed system (intranet or Internet). Compared to mobile objects, mobile agents also represent someone; they can perform autonomous actions on behalf of a user or another agent. This paper describes the Mobile Objects and Agents (MOA) project at the Open Group Research Institute. The obvious question is why yet another mobile agent system? There were a few reasons. None of the existing systems at the time of starting the project were mature enough to be used as a starting point for our wor...

show abstract

“…It represents seamless migration at the granularity of individual processes, and has been a research focus on many experimental operating systems. Examples include Charlotte [3], Sprite [4], Demos [5], V [6], Condor [7], and Mach [8]. These independent validation efforts have shown beyond reasonable doubt that process migration can indeed be implemented with acceptable efficiency.…”

Section: Introductionmentioning

confidence: 99%

A Component-based Intelligent Seamless Service Migration Mechanism and Flexible Communication Protocol in Pervasive Computing Systems

Cai

Peng

Zhang

et al. 2014

IJCIS

View full text Add to dashboard Cite

In pervasive computing systems, service selection and fault tolerance are two primary factors, which determines reliability and efficient of service selection system. In this paper, according on ANN-based (Artificial Neural Network) service selection model, we extend the definition and formal description of service, and propose the architecture of service migration system, evaluation method, judgment theorems of triggering and a serviceoriented seamless migration (SOSM) algorithm in pervasive computing systems. We also propose the flexible communication protocol for service seamless migration activity based on mobile agent computing network. We have implemented the SOSM mechanism and flexible communication protocol in an intelligent service selection prototype (ISSPS) system, which provide the pervasive web services for users in pervasive computing environment. The results show that the proposed service migration mechanism is not only reliable but also efficient.

show abstract

Preemptable remote execution facilities for the V-system

Cited by 196 publications

References 10 publications

Proactive process-level live migration and back migration in HPC environments

Proactive process-level live migration and back migration in HPC environments

Mobile Objects and Agents (MOA)

A Component-based Intelligent Seamless Service Migration Mechanism and Flexible Communication Protocol in Pervasive Computing Systems

Contact Info

Product

Resources

About