Happens-before

In computer science, the happened-before relation (denoted: $\to \;$) is a relation between the result of two events, such that if one event should happen before another event, the result must reflect that, even if those events are in reality executed out of order (usually to optimize program flow). This involves ordering events based on the potential causal relationship of pairs of events in a concurrent system, especially asynchronous distributed systems. It was formulated by Leslie Lamport.

The happened-before relation is formally defined as the least strict partial order on events such that:
* If events $a \;$ and $b \;$ occur on the same process, $a \to b\;$ if the occurrence of event $a \;$ preceded the occurrence of event $b \;$.
* If event $a \;$ is the sending of a message and event $b \;$ is the reception of the message sent in event $a \;$, $a \to b\;$.

If two events happen in different isolated processes (that do not exchange messages directly or indirectly via third-party processes), then the two processes are said to be concurrent, that is neither $a \to b$ nor $b \to a$ is true.

If there are other causal relationships between events in a given system, such as between the creation of a process and its first event, these relationships are also added to the definition.
For example, in some programming languages such as Java, C, C++ or Rust, a happens-before edge exists if memory written to by statement A is visible to statement B, that is, if statement A completes its write before statement B starts its read.

Like all strict partial orders, the happened-before relation is '' transitive'', ''irreflexive'' (and vacuously, '' asymmetric''), i.e.:
* $\forall a, b, c$, if $a \to b\;$ and $b \to c\;$, then $a \to c\;$ (transitivity). This means that for any three events $a, b, c$, if $a$ happened before $b$, and $b$ happened before $c$, then $a$ must have happened before $c$.
* $\forall a, a \nrightarrow a$ (irreflexivity). This means that no event can happen before itself.
* $\forall a, b,$ if $a \to b$ then $b \nrightarrow a$ (asymmetry). This means that for any two events $a, b$, if $a$ happened before $b$ then $b$ cannot have happened before $a$.

Let us observe that the asymmetry property directly follows from the previous properties: by contradiction, let us suppose that $\forall a, b,$ we have $a \to b\;$ and $b \to a$. Then by transitivity we have $a \to a,$ which contradicts irreflexivity.

The processes that make up a distributed system have no knowledge of the happened-before relation unless they use a logical clock, like a Lamport clock or a vector clock. This allows one to design algorithms for mutual exclusion, and tasks like debugging or optimising distributed systems.

Byzantine Faults and the Impossibility of Detection

In distributed systems, the happened-before relation can be accurately tracked under crash failures using vector clocks, their variants, and other causality tracking mechanisms. However, under Byzantine faults, where processes may behave arbitrarily or maliciously, it is fundamentally impossible to detect the happened-before relation . The intuitive reasoning for this is that Byzantine processes can forge or manipulate metadata, making it impossible to determine true causal dependencies.

See also

* Race condition
* Java memory model
* Lamport timestamps
* Logical clock

Citations

References

*

{{DEFAULTSORT:Happened-Before
Logical clock algorithms
Distributed computing problems
Transitive relations