Skip to content

Commit 538e3bd

Browse files
authored
Merge pull request ceph#56646 from zdover23/wip-doc-2024-04-02-dev-peering-concepts-2-of-3
doc/dev: refine "Concepts" 2 of 3 Reviewed-by: Anthony D'Atri <[email protected]>
2 parents 378890f + 7bb3528 commit 538e3bd

File tree

1 file changed

+20
-23
lines changed

1 file changed

+20
-23
lines changed

doc/dev/peering.rst

Lines changed: 20 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -45,39 +45,36 @@ Concepts
4545
*acting set*.
4646

4747
*replica*
48-
a non-primary OSD in the *acting set* for a placement group
49-
(and who has been recognized as such and *activated* by the primary).
48+
a non-primary OSD in the *acting set* of a placement group. A replica has
49+
been recognized as a non-primary OSD and has been *activated* by the
50+
primary.
5051

5152
*stray*
52-
an OSD who is not a member of the current *acting set*, but
53-
has not yet been told that it can delete its copies of a
54-
particular placement group.
53+
an OSD that is not a member of the current *acting set* and has not yet been
54+
told to delete its copies of a particular placement group.
5555

5656
*recovery*
57-
ensuring that copies of all of the objects in a PG
58-
are on all of the OSDs in the *acting set*. Once
59-
*peering* has been performed, the primary can start
60-
accepting write operations, and *recovery* can proceed
61-
in the background.
57+
the process of ensuring that copies of all of the objects in a PG are on all
58+
of the OSDs in the *acting set*. After *peering* has been performed, the
59+
primary can begin accepting write operations and *recovery* can proceed in
60+
the background.
6261

6362
*PG info*
64-
basic metadata about the PG's creation epoch, the version
65-
for the most recent write to the PG, *last epoch started*, *last
66-
epoch clean*, and the beginning of the *current interval*. Any
67-
inter-OSD communication about PGs includes the *PG info*, such that
68-
any OSD that knows a PG exists (or once existed) also has a lower
69-
bound on *last epoch clean* or *last epoch started*.
63+
basic metadata about the PG's creation epoch, the version for the most
64+
recent write to the PG, the *last epoch started*, the *last epoch clean*,
65+
and the beginning of the *current interval*. Any inter-OSD communication
66+
about PGs includes the *PG info*, such that any OSD that knows a PG exists
67+
(or once existed) and also has a lower bound on *last epoch clean* or *last
68+
epoch started*.
7069

7170
*PG log*
72-
a list of recent updates made to objects in a PG.
73-
Note that these logs can be truncated after all OSDs
74-
in the *acting set* have acknowledged up to a certain
75-
point.
71+
a list of recent updates made to objects in a PG. These logs can be
72+
truncated after all OSDs in the *acting set* have acknowledged the changes.
7673

7774
*missing set*
78-
Each OSD notes update log entries and if they imply updates to
79-
the contents of an object, adds that object to a list of needed
80-
updates. This list is called the *missing set* for that <OSD,PG>.
75+
the set of all objects that have not yet had their contents updated to match
76+
the log entries. The missing set is collated by each OSD. Missing sets are
77+
kept track of on an ``<OSD,PG>`` basis.
8178

8279
*Authoritative History*
8380
a complete, and fully ordered set of operations that, if

0 commit comments

Comments
 (0)