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

Shrivastava, SK; McCue, Daniel L.

doi:10.1109/71.273048

Cited by 20 publications

(5 citation statements)

References 27 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The material of this section is taken from some of our published papers on Arjuna. [3][4][5] Section 3 gives a brief overview of some of the middleware transaction standards that are relevant to the various transaction services that Arjuna supports. Section 4 describes how the Arjuna system was adapted for use as a transaction service for CORBA (OTS) and Java middleware (JTS); here we also compare and contrast the functionality of the original Arjuna system with that of Java EE component based middleware.…”

Section: Introductionmentioning

confidence: 99%

“…Sufficient details of the system are presented here to enable the readers to follow the subsequent discussions concerning middleware transaction services. The material of this section is taken from some of our published papers on Arjuna 3‐5 . Section 3 gives a brief overview of some of the middleware transaction standards that are relevant to the various transaction services that Arjuna supports.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

The evolution of the Arjuna transaction processing system

Little

Shrivastava

2021

Softw Pract Exp

View full text Add to dashboard Cite

The Arjuna transaction processing system began life in the mid-1980s as an academic research project to examine the use of object-oriented techniques in the development of fault-tolerant distributed systems. Thirty-five years later, and available in open source form, it forms an integral part of various middleware products from Red Hat where it is used to provide ACID as well as non-ACID transaction services. This journey from an academic to a commercial environment has been neither easy nor smooth but it has been interesting from many different perspectives. This article gives an overview of this journey, discusses the features of Arjuna that enables it to support a wide variety of transaction services and concludes by presenting lessons learned.

show abstract

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

The evolution of the Arjuna transaction processing system

Little

Shrivastava

2021

Softw Pract Exp

View full text Add to dashboard Cite

show abstract

“…Indeed, a large class of applications exists for which the full power of a DBMS may not be required, but for which reliable, concurrent access to shared data is a crucial requirement. As a result, transaction facilities are now being supported in many file systems such as Camelot [1] and Arjuna [2].…”

Section: Introductionmentioning

confidence: 99%

Advanced transaction processing in multilevel secure file stores

Bertino

Jajodia²,

Mancini³

et al. 1998

IEEE Trans. Knowl. Data Eng.

View full text Add to dashboard Cite

The concurrency control requirements for transaction processing in a multilevel secure file system are different from those in conventional transaction processing systems. In particular, there is the need to coordinate transactions at different security levels avoiding both potential timing covert channels and the starvation of transactions at higher security levels. Suppose a transaction at a lower security level attempts to write a data item that is being read by a transaction at a higher security level. On the one hand, a timing covert channel arises if the transaction at the lower security level is either delayed or aborted by the scheduler. On the other hand, the transaction at the high security level may be subjected to an indefinite delay if it is forced to abort repeatedly. This paper extends the classical two-phase locking mechanism to multilevel secure file systems. The scheme presented here prevents potential timing covert channels and avoids the abort of higher level transactions nonetheless guaranteeing serializability. The programmer is provided with a powerful set of linguistic constructs that supports exception handling, partial rollback, and forward recovery. The proper use of these constructs can prevent the indefinite delay in completion of a higher level transaction, and allows the programmer to trade off starvation with transaction isolation.

show abstract

“…[2][3][4][5] Several other systems offer fault management using the natural redundancy of the distributed system without requiring specific hardware support. [6][7][8][9][10] Star fills this gap and is built totally outside the operating system. The challenge is to show that software fault tolerance can be efficiently implemented in a standardized environment.…”

Section: Introductionmentioning

confidence: 99%

The STAR fault manager for distributed operating environments. design, implementation and performance

Sens¹,

Folliot²

1998

Softw: Pract. Exper.

View full text Add to dashboard Cite

This paper presents the design, implementation and performance evaluation of a software fault manager for distributed applications. Dubbed Star, it uses the natural redundancy existing in networks of workstations to offer a high level of fault tolerance. Fault management is transparent to the supported parallel applications. To improve the response time of fault-tolerant applications, Star implements non-blocking and incremental checkpointing to perform an efficient backup of process state. Moreover, Star is application independent, highly configurable. Star actually runs on top of SunOs and is easily portable to UNIX™-like operating systems. The current implementation is based on independent checkpointing and message logging. Measurements show the efficiency and the limits of this implementation.The challenge is to show that a software approach to fault tolerance can efficiently be implemented in a standard networked environment.

show abstract

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

Cited by 20 publications

References 27 publications

The evolution of the Arjuna transaction processing system

The evolution of the Arjuna transaction processing system

Advanced transaction processing in multilevel secure file stores

The STAR fault manager for distributed operating environments. design, implementation and performance

Contact Info

Product

Resources

About