A communication-induced checkpointing protocol that ensures rollback-dependency trackability

Abstract

Considering an application in which processes take local checkpoints independently (called basic checkpoints), this paper develops a protocol that forces them to take some additional local checkpoints (called forced checkpoints) in order that the resulting checkpoint and communication pattern satisfies the Rollback Dependency Trackability (RDT) property. This property states that all dependencies between local checkpoints are on-line trackable by using a transitive dependency vectol:Compared to other protocols ensuring the RDT property, the proposed protocol is less conservative in the sense that it takes less additional local checkpoints. It attains this goal by a subtle tracking of causal dependencies on already taken checkpoints; this tracking is then used to prevent the occurrence of hidden dependencies. As indicated by simulation study, the proposed protocol compares favorably with other protocols; moreovec it additionally associates on-the-jly with each local checkpoint G the minimum global checkpoint to which C belongs.

A Review of Fault Tolerant Checkpointing Protocols for Mobile Computing Systems

“…Communication-induced checkpointing avoids the domino-effect without requiring all checkpoints to be coordinated [12], [33], [55]. In these protocols, processes take two kinds of checkpoints, local and forced.…”

A Low-Overhead Non-Block Check Pointing and Recovery Approach for Mobile Computing Environment

“…Besides these two fundamental approaches there is another approach known as communication induced check pointing approach (J. Tsai et al, 1998;R. Baldoni et al, 1997;J.…”

Anti-message Logging Based Coordinated Checkpointing Protocol for Deterministic Mobile Computing Systems

“…In the case of a fault, processes rollback to the last checkpointed state. Communication-induced Checkpointing: It avoids the domino-effect without requiring all checkpoints to be coordinated [2], [7], [9]. In these protocols, processes take two kinds of checkpoints, local and forced.…”

“…To recover from a failure, the system restarts its execution from a previous consistent global state saved on the stable storage during fault-free execution. In distributed systems, checkpointing can be independent, coordinated [3], [8], [11] or quasi-synchronous [2], [9]. Message Logging is also used for fault tolerance in distributed systems [14].…”