Synchronizing clocks in the presence of faults
Journal of the ACM (JACM)
The distributed firing squad problem
SIAM Journal on Computing
Knowledge and common knowledge in a distributed environment
Journal of the ACM (JACM)
Early stopping in Byzantine agreement
Journal of the ACM (JACM)
Knowledge and common knowledge in a byzantine environment: crash failures
Information and Computation
The possibility and the complexity of achieving fault-tolerant coordination
PODC '92 Proceedings of the eleventh annual ACM symposium on Principles of distributed computing
Reasoning about knowledge
Possible and Impossible Self-Stabilizing Digital ClockSynchronization in General Graphs
Real-Time Systems - Special issue on global time in large scale distributed real-time systems, part I
Self-stabilization
Self-stabilizing clock synchronization in the presence of Byzantine faults
Journal of the ACM (JACM)
Common knowledge and consistent simultaneous coordination
Distributed Computing
Continuous Consensus with Failures and Recoveries
DISC '08 Proceedings of the 22nd international symposium on Distributed Computing
Revisiting simultaneous consensus with crash failures
Journal of Parallel and Distributed Computing
Self-stabilizing Byzantine digital clock synchronization
SSS'06 Proceedings of the 8th international conference on Stabilization, safety, and security of distributed systems
Hi-index | 0.00 |
Consider a fully connected network where up to t processes may crash, and all processes start in an arbitrary memory state. The self-stabilizing firing squad problem consists of eventually guaranteeing simultaneous response to an external input. This is modeled by requiring that the non-crashed processes "fire" simultaneously if some correct process received an external "go " input, and that they only fire as a response to some process receiving such an input. This paper presents Fire-Squad , the first self-stabilizing firing squad algorithm. The Fire-Squad algorithm is optimal in two respects: (a) Once the algorithm is in a safe state, it fires in response to a go input as fast as any other algorithm does, and (b) Starting from an arbitrary state, it converges to a safe state as fast as any other algorithm does.