From 95d46b579751591fb269c259d8b25fca0654c334 Mon Sep 17 00:00:00 2001 From: Marco Realacci Date: Tue, 25 Mar 2025 15:22:04 +0100 Subject: [PATCH] vault backup: 2025-03-25 15:22:04 --- Concurrent Systems/notes/8 - Enhancing Liveness Properties.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Concurrent Systems/notes/8 - Enhancing Liveness Properties.md b/Concurrent Systems/notes/8 - Enhancing Liveness Properties.md index 3d54c65..4e59d5b 100644 --- a/Concurrent Systems/notes/8 - Enhancing Liveness Properties.md +++ b/Concurrent Systems/notes/8 - Enhancing Liveness Properties.md @@ -9,7 +9,7 @@ Can we take the most basic protocol that satisfies the most basic liveness prope >[!question] Why is it different from lock/unlock? >Because this allows failures, and they can also happen in the contention-free period. -**PROBLEM:** to distinguish a failure from a long delay, we need objects called ***failure detectors***, that provide processes information on the failed processes of the system. According to the type/quality of the info, several F.D.s can be defined. +**PROBLEM:** to distinguish a failure from a long delay, we need objects called ***failure detectors*** (FDs), that provide processes information on the failed processes of the system. According to the type/quality of the info, several FDs can be defined. **Eventually restricted leadership:** given a non-empty set of process IDs X, the failure detector $\Omega_{X}$ provides each process a local variable `ev_leader(X)` such that: 1. *(Validity)* `ev_leader(x)` always contains a process ID