1,071 research outputs found
Reliability Issues in Distributed Operating Systems
Distributed systems span a wide spectrum in the design space. In this paper we will look at the various kinds and discuss some of the reliability issues involved. In the first half of the paper we will concentrate on the causes of unreliability, illustrating these with some general solutions and examples. Among the issues treated are interprocess communication, machine crashes, server redundancy, and data integrity. In the second half of the paper, we will examine one distributed operating system, Amoeba, to see how reliability issues have been handled in at least one real system, and how the pieces fit together. 1. INTRODUCTION It is difficult to get two computer scientists to agree on what a distributed system is. Rather than attempt to formulate a watertight definition, which is probably impossible anyway, we will divide these systems into three broad categories: - Closely coupled systems - Loosely coupled systems - Barely coupled systems The key issue that distinguishes these syst..
Using Sparse Capabilities in a Distributed Operating System
this paper we discuss a system, Amoeba, that uses capabilities for naming and protecting objects. In contrast to traditional, centralized operating systems, in which capabilities are managed by the operating system kernel, in Amoeba all the capabilities are managed directly by user code. To prevent tampering, the capabilities are protected cryptographically. The paper describes a variety of the issues involved, and gives four different ways of dealing with the access rights
Transparent Fault-tolerance in Parallel Orca Programs
With the advent of large-scale parallel computing systems, making parallel programs fault-tolerant becomes an important problem, because the probability of a failure increases with the number of processors. In this paper, we describe a very simple scheme for rendering a class of parallel Orca programs fault-tolerant. Also, we discuss our experience with implementing this scheme on Amoeba. Our approach works for parallel applications that are not interactive. The approach is based on making a globally consistent checkpoint from time to time and rolling back to the last checkpoint when a processor fails. Making a consistent global checkpoint is easy in Orca, because its implementation is based on reliable broadcast. The advantages of our approach are its simplicity, ease of implementation, low overhead, and transparency to the Orca programmer. 1
Performance of the Amoeba Distributed Operating System
Amoeba is a capability‐based distributed operating system designed for high‐performance interactions between clients and servers using the well‐known RPC model. The paper starts out by describing the architecture of the Amoeba system, which is typified by specialized components such as workstations, several services, a processor pool, and gateways that connect other Amoeba systems transparently over wide‐area networks. Next the RPC interface is described. The paper presents performance measurements of the Amoeba RPC on unloaded and loaded systems. The time to perform the simplest RPC between two user processes has been measured to be 1‐4 ms. Compared to SUN 3/50's RPC, Amoeba has one ninth of the delay, and over three times the throughput. Finally we describe the Amoeba file server. The Amoeba file server is so fast that it is limited by the communication bandwidth. To the best of our knowledge this is the fastest file server yet reported in the literature for this class of hardware. Copyright © 1989 John Wiley & Sons, Lt
The Amoeba Distributed Operating System - A Status Report
As the price of CPU chips continues to fall rapidly, it will soon be economically feasible to build computer systems containing a large number of processors. The question of how this computing power should be organized, and what kind of operating system is appropriate then arises. Our research during the past decade has focused on these issues and led to the design of a distributed operating system, called Amoeba, that is intended for systems with large numbers of computers. In this paper we describe Amoeba, its philosophy, its design, its applications, and some experience with it. 1
Construction of silicon nanocolumns with the scanning tunneling microscope
Voltage pulses to a scanning tunneling microscope (STM) are used to construct silicon columns of 30–100 Å diameter and up to 200 Å height on a silicon surface and on the end of a tungsten probe. These nanocolumns have excellent conductivity and longevity, and they provide an exceptional new ability to measure the shapes of nanostructures with a STM. This construction methodology and these slender yet robust columns provide a basis for nanoscale physics, lithography, and technology
Beyond UNIX - A True Distributed System for the 1990s
UNIX has been around now for almost 20 years. At the time UNIX began, most departments felt themselves well-endowed indeed if they owned a single PDP-11/45 with 256K memory and a 2.5M RK05 disk. Nowadays a laptop would be embarrassed to have only that. It is our hypothesis that UNIX is no longer the appropriate kind of operating system for the 1990s. In this paper, a new system, Amoeba, will be described, that we believe meets the requirements for distributed computing in the 1990s
Efficient routing on complex networks
In this letter, we propose a new routing strategy to improve the
transportation efficiency on complex networks. Instead of using the routing
strategy for shortest path, we give a generalized routing algorithm to find the
so-called {\it efficient path}, which considers the possible congestion in the
nodes along actual paths. Since the nodes with largest degree are very
susceptible to traffic congestion, an effective way to improve traffic and
control congestion, as our new strategy, can be as redistributing traffic load
in central nodes to other non-central nodes. Simulation results indicate that
the network capability in processing traffic is improved more than 10 times by
optimizing the efficient path, which is in good agreement with the analysis.Comment: 4 pages, 4 figure
- …