An overview of the Arjuna distributed programming system

Shrivastava, SK; Dixon, GN; Parrington, GD

doi:10.1109/52.62934

Cited by 143 publications

(39 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…We have arrived at the system structuring ideas presented in the previous section based on our experience of designing and implementing a distributed programming system called Arjuna [11,23,29]. Arjuna is an object-oriented programming system implemented in C++ that provides a set of tools for the construction of fault-tolerant distributed applications constructed according to the model discussed in section 2.…”

Section: Case Study: An Examination Of Arjunamentioning

confidence: 99%

“…For example, systems such as Argus [14], Arjuna [11,23,29], SOS [28] and Guide [4] have emphasised fault-tolerance and distribution aspects, languages such as PS-Algol [3], Galileo [2] and E [25] have contributed to our understanding of persistence as a language feature, while efforts such as [12] have contributed to the understanding of the design of object stores and their relationship to database systems. We build on these efforts and describe the necessary features of a modular distributed programming system supporting persistent objects.…”

Section: Basic Concepts and Assumptionsmentioning

confidence: 99%

“…Section 3 then identifies the major system components and their interfaces and the interactions of those components. The proposed system structure is based upon a retrospective examination of a distributed system -Arjuna [11,23,29] -built at Newcastle. The main aspects of this system are presented in section 4 and are examined in light of the discussion in the preceding section.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Structuring fault-tolerant object systems for modularity in a distributed environment

Shrivastava

McCue

1994

IEEE Trans. Parallel Distrib. Syst.

Self Cite

View full text Add to dashboard Cite

The object-oriented approach to system structuring has found widespread acceptance among designers and developers of robust computing systems. In this paper we propose a system structure for distributed programming systems that support persistent objects and describe how such properties as persistence, recoverability etc.can be implemented. The proposed structure is modular, permitting easy exploitation of any distributed computing facilities provided by the underlying system. An existing system constructed according to the principles espoused here is examined to illustrate the practical utility of the proposed approach to system structuring.

show abstract

Section: Case Study: An Examination Of Arjunamentioning

confidence: 99%

Section: Basic Concepts and Assumptionsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Structuring fault-tolerant object systems for modularity in a distributed environment

Shrivastava

McCue

1994

IEEE Trans. Parallel Distrib. Syst.

Self Cite

View full text Add to dashboard Cite

show abstract

“…Arjuna is an object-oriented programming system that provides atomic actions on objects using C++ classes [71]. The atomic actions ensure that all operations support the properties of serializability, failure atomicity, and permanence of effect.…”

Section: Other System-level Approachesmentioning

confidence: 99%

Fault Tolerance in Critical Information Systems

Knight¹,

Elder²

View full text Add to dashboard Cite

Public reporting burden for the collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to a penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Critical infrastructure applications provide services upon which society depends heavily; such applications require constant, dependable operation in the face of various failures, natural disasters, and other disruptive events that might cause a loss of service. These applications are themselves dependent on distributed information systems for all aspects of their operation, so survivability of these critical information systems is an important issue. Survivability is the ability of a system to continue to provide service, though possibly alternate or degraded, in the face of various types of failure and disruption. A fundamental mechanism by which survivability can be achieved in critical information systems is fault tolerance. Much of the literature on fault-tolerant distributed systems focuses on tolerance of local faults by detecting and masking the effects of those faults. I describe a direction for fault tolerance in the face of non-local faults-faults whose effects have significant non-local impact, sometimes widespread and sometimes catastrophic-where often the effects of these faults cannot be masked using available resources. The goal is to recognize these non-local faults through detection and analysis, then to provide continued service (possibly alternate or degraded) by reconfiguring the system in response to these faults.A specification-based approach to fault tolerance, called RAPTOR, is presented that enables systematic structuring of formal specifications for error detection and recovery, utilizes a translator to synthesize portions of the implementation from the formal specifications, and provides an implementation architecture supporting fault-tolerance activities. The RAPTOR approach consists of three specifications describing the fault-tolerant system, the errors to be detected, and the actions to take to recover from those errors. The RAPTOR System includes a synthesizer, the Fault Tolerance Translator, to generate implementation of code components from the specifications to perform error detection and recovery activities. In addition, a novel implementation architecture incorporates the generated code as part of an infrastructure supporting fault tolerance at both the node and syst...

show abstract

“…In [28,29] an extension is added to C++, LISP and Ada to support the recovery from failures. In [30,31], a C++ extension with the transactional properties are added in to the programming language that can be used in interaction failure recovery. In these references, the explicit client or server abort or commit is supported by extended APIs to the original language.…”

Section: Application Implementation Language Supportmentioning

confidence: 99%

Robust collaborative services interactions under system crashes and network failures

Wang¹

View full text Add to dashboard Cite

An overview of the Arjuna distributed programming system

Cited by 143 publications

References 6 publications

Structuring fault-tolerant object systems for modularity in a distributed environment

Structuring fault-tolerant object systems for modularity in a distributed environment

Fault Tolerance in Critical Information Systems

Robust collaborative services interactions under system crashes and network failures

Contact Info

Product

Resources

About