2003 International Conference on Dependable Systems and Networks, 2003. Proceedings.
DOI: 10.1109/dsn.2003.1209965
|View full text |Cite
|
Sign up to set email alerts
|

How bad are wrong suspicions? towards adaptive distributed protocols

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
31
0

Publication Types

Select...
4
2

Relationship

1
5

Authors

Journals

citations
Cited by 12 publications
(31 citation statements)
references
References 11 publications
0
31
0
Order By: Relevance
“…Therefore, the issue of tuning these timeouts is a crucial point in the design of an efficient failure detector. Too small timeouts increase wrong suspicions, which, may harm the performance of the higher level consensus protocol [17]. On the other hand, too large timeouts increase the detection latency of the service, imposing heavy overheads to those runs on which failures occur [4,23].…”
Section: Related Workmentioning
confidence: 99%
See 4 more Smart Citations
“…Therefore, the issue of tuning these timeouts is a crucial point in the design of an efficient failure detector. Too small timeouts increase wrong suspicions, which, may harm the performance of the higher level consensus protocol [17]. On the other hand, too large timeouts increase the detection latency of the service, imposing heavy overheads to those runs on which failures occur [4,23].…”
Section: Related Workmentioning
confidence: 99%
“…In fact, in the simulations conducted, the failure detector module was replaced by a mock implementation that always returned an empty set of suspected processes, obviating the need for exchanging failure detection messages. Nevertheless, the simulation results presented in [17] show that even this very naive implementation of a slowness oracle is able to increase the performance of consensus in as much as 17% for a lightly loaded system.…”
Section: Raul Ceretta Nunesmentioning
confidence: 99%
See 3 more Smart Citations