IEEE Transactions on Parallel and Distributed Systems · 1998 · 53 citations · 19 references
ComputingCommunicationComputer EngineeringFault ToleranceFault-tolerant ComputingFault-tolerant SystemsData SynchronizationFault Tolerance In CommunicationFault-tolerant CommunicationReliable Distributed SystemsRollback RecoverySoftware Fault ToleranceCheckpointingCheckpointsCommunication PatternsCommunication-induced CheckpointingFormal SpecificationsProtocol ArchitectureRollbackTransitive Dependency Analysis
Rollback-Dependency Trackability (RDT) is a property that states that all rollback dependencies between local checkpoints are on-line trackable by using a transitive dependency vector. In this paper, we address three fundamental issues in the design of communication-induced checkpointing protocols that ensure RDT. First, we prove that the following intuition commonly assumed in the literature is in fact false: If a protocol forces a checkpoint only at a stronger condition, then it must take, at most, as many forced checkpoints as a protocol based on a weaker condition. This result implies that the common approach of sharpening the checkpoint-inducing condition by piggybacking more control information on each message may not always yield a more efficient protocol. Next, we prove that there is no optimal on-line RDT protocol that takes fewer forced checkpoints than any other RDT protocol for all possible communication patterns. Finally, since comparing checkpoint-inducing conditions is not sufficient for comparing protocol performance, we present some formal techniques for comparing the performance of several existing RDT protocols.
19
K. Mani Chandy, Leslie Lamport · ACM Transactions on Computer Systems · 1985 · 2.4K citations · Full text
System structure for software fault tolerance
Brian Randell · ACM SIGPLAN Notices · 1975 · 1.5K citations · Full text
System structure for software fault tolerance
Brian Randell · IEEE Transactions on Software Engineering · 1975 · 1.1K citations