Skip to content

Commit 512e2dc

Browse files
committed
doc/dev: refine "Concepts" 3 of 3
Refine the third third of the entries in the section "Concepts" in doc/dev/peering.rst. Signed-off-by: Zac Dover <[email protected]>
1 parent a21870a commit 512e2dc

File tree

1 file changed

+10
-13
lines changed

1 file changed

+10
-13
lines changed

doc/dev/peering.rst

Lines changed: 10 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -77,24 +77,22 @@ Concepts
7777
kept track of on an ``<OSD,PG>`` basis.
7878

7979
*Authoritative History*
80-
a complete, and fully ordered set of operations that, if
81-
performed, would bring an OSD's copy of a Placement Group
82-
up to date.
80+
a complete and fully-ordered set of operations that bring an OSD's copy of a
81+
Placement Group up to date.
8382

8483
*epoch*
85-
a (monotonically increasing) OSD map version number
84+
a (monotonically increasing) OSD map version number.
8685

8786
*last epoch start*
88-
the last epoch at which all nodes in the *acting set*
89-
for a particular placement group agreed on an
90-
*authoritative history*. At this point, *peering* is
91-
deemed to have been successful.
87+
the last epoch at which all nodes in the *acting set* for a given placement
88+
group agreed on an *authoritative history*. At the start of the last epoch,
89+
*peering* is deemed to have been successful.
9290

9391
*up_thru*
9492
before a primary can successfully complete the *peering* process,
9593
it must inform a monitor that is alive through the current
9694
OSD map epoch by having the monitor set its *up_thru* in the osd
97-
map. This helps peering ignore previous *acting sets* for which
95+
map. This helps peering ignore previous *acting sets* for which
9896
peering never completed after certain sequences of failures, such as
9997
the second interval below:
10098

@@ -104,10 +102,9 @@ Concepts
104102
- *acting set* = [B] (B restarts, A does not)
105103

106104
*last epoch clean*
107-
the last epoch at which all nodes in the *acting set*
108-
for a particular placement group were completely
109-
up to date (both PG logs and object contents).
110-
At this point, *recovery* is deemed to have been
105+
the last epoch at which all nodes in the *acting set* for a given placement
106+
group were completely up to date (this includes both the PG's PG logs and
107+
the PG's object contents). At this point, *recovery* is deemed to have been
111108
completed.
112109

113110
Description of the Peering Process

0 commit comments

Comments
 (0)