Decentralized Resource Management and Fault-Tolerance for Distributed CORBA Applications

Assigning an application’s fault-tolerance properties (e.g., replication style, checkpointing frequency) statically, and in an arbitrary manner, can lead to the application not achieving its target resilience and performance. The resource management infrastructure that we have developed transparently determines a CORBA application’s resource usage and its rate/pattern of invocation across a distributed system. Using this information, our infrastructure makes more informed decisions about the application’s fault-tolerance properties, and dynamically adapts these decisions, as faults occur, and as resources are added and removed from the system. We have designed our prototype to be decentralized so that it is scalable and does not itself constitute a single point of failure.

[1]  Priya Narasimhan,et al.  Estimating Fault-Detection and Fail-Over Times for Nested Real-Time CORBA Applications , 2003, PDPTA.

[2]  Daniel Pierre Bovet,et al.  Understanding the Linux Kernel , 2000 .

[3]  John R. White,et al.  Linkers and Loaders , 1972, CSUR.

[4]  Yair Amir,et al.  A low latency, loss tolerant architecture and protocol for wide area group communication , 2000, Proceeding International Conference on Dependable Systems and Networks. DSN 2000.

[5]  Roger Faulkner,et al.  The Process File System and Process Model in UNIX System V , 1991, USENIX Winter.

[6]  Priya Narasimhan,et al.  Transparent fault tolerance for corba , 1999 .

[7]  Lisa Cingiser DiPippo,et al.  Real-time CORBA , 1997, Proceedings Third IEEE Real-Time Technology and Applications Symposium.

[8]  Priya Narasimhan,et al.  Experiences, strategies, and challenges in building fault-tolerant CORBA systems , 2004, IEEE Transactions on Computers.