25th IEEE Symposium on Reliable Distributed Systems (SRDS'06) Solving Consensus Using Structural Failure Models Leeds, United Kingdom October 02-October 04 ISBN: 0-7695-2677-2
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/SRDS.2006.44
Failure models characterise the expected component failures in fault-tolerant computing. In the context of dis- tributed systems, a failure model usually consists of two parts: a functional part specifying in what way individual processing entities may fail and a structural part specifying the potential scope of failures within the system. Such mod- els must be expressive enough to cover all relevant practical situations, but must also be simple enough to allow uncom- plicated reasoning about fault-tolerant algorithms. Usu- ally, an increase in expressiveness complicates formal rea- soning, but enables more accurate models that allow to im- prove the assumption coverage and resilience of solutions. In this paper, we introduce the structural failure model class DiDep that allows to specify directed dependent fail- ures, which, for example, occur in the area of intrusion tolerance and security. DiDep is a generalisation of pre- vious classes for undirected dependent failures, namely the general adversary structures, the fail-prone systems, and the core and survivor sets, which we show to be equivalent. We show that the increase in expressiveness of DiDep does not significantly penalise the simplicity of corresponding mod- els by giving an algorithm that transforms any Consensus algorithm for undirected dependent failures into a Consen- sus algorithm for a DiDep model. We characterise the im- proved resilience obtained with DiDep and show that cer- tain models even allow to circumvent the famous FLP im- possibility result.
Citation:
Timo Warns, Felix C. Freiling, Wilhelm Hasselbring, "Solving Consensus Using Structural Failure Models," srds, pp.212-224, 25th IEEE Symposium on Reliable Distributed Systems (SRDS'06), 2006 Usage of this product signifies your acceptance of the Terms of Use. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||