1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
//! Application events the runtime journals on a node's own behalf.
/// Events the runtime journals as a node takes up the primary role,
/// before it serves its first client.
///
/// They go through the journal like any client event, and that is the
/// point: replicas receive them in the stream, and every replay — from
/// genesis, from a snapshot, on a promoted replica — applies them again,
/// in order. Nothing the application's state depends on bypasses the
/// journal, so recovery can only reproduce the state the node had.
///
/// `Vec` rather than an iterator: both sets are built once at startup
/// from operator configuration and consumed once, off any hot path.