You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -158,9 +158,9 @@ When the primary collects its JV quorum:
158
158
159
159
### Protocol: Request/View
160
160
161
-
#### `request_view`
161
+
#### `get_view`
162
162
163
-
A backup sends a `command=request_view` to the primary of a view when any of the following occur:
163
+
A backup sends a `command=get_view` to the primary of a view when any of the following occur:
164
164
165
165
- the backup learns about a newer view via a `command=commit` message, or
166
166
- the backup learns about a newer view via a `command=prepare` message, or
@@ -170,7 +170,7 @@ A backup sends a `command=request_view` to the primary of a view when any of the
170
170
171
171
#### `view`
172
172
173
-
When a `status=normal` primary receives `command=request_view`, it replies with a `command=view`.
173
+
When a `status=normal` primary receives `command=get_view`, it replies with a `command=view`.
174
174
`command=view` includes:
175
175
- The view's current suffix — the headers of the latest messages in the view.
176
176
- The current checkpoint (see [State Sync](./sync.md)).
@@ -187,7 +187,7 @@ A `view` contains the following headers (which may overlap):
187
187
188
188
### Protocol: Repair Journal
189
189
190
-
`request_headers` and `headers` repair gaps or breaks in a replica's journal headers.
190
+
`get_headers` and `headers` repair gaps or breaks in a replica's journal headers.
191
191
Repaired headers are a prerequisite for [repairing prepares](#protocol-repair-wal).
192
192
193
193
Because the headers are repaired backwards (from the head) by hash-chaining, it is safe for both backups and transitioning primaries.
@@ -210,9 +210,9 @@ During repair, missing/damaged prepares are requested & repaired chronologically
210
210
- improves the chances that older entries will be available, i.e. not yet overwritten
211
211
- enables better pipelining of repair and commit.
212
212
213
-
In response to a `request_prepare`:
213
+
In response to a `get_prepare`:
214
214
215
-
-Reply the `command=prepare` with the requested prepare, if available and valid.
215
+
-Respond with the `command=prepare` message with the requested prepare, if available and valid.
216
216
- Otherwise do not reply. (e.g. the corresponding slot in the WAL is corrupt)
217
217
218
218
Per [PAR's CTRL Protocol](https://www.usenix.org/system/files/conference/fast18/fast18-alagappan.pdf), we do not nack corrupt entries, since they _might_ be the prepare being requested.
@@ -226,9 +226,9 @@ The replica stores the latest reply to each active client.
226
226
227
227
During repair, corrupt client replies are requested & repaired.
228
228
229
-
In response to a `request_reply`:
229
+
In response to a `get_reply`:
230
230
231
-
- Respond with the `command=reply` (the requested reply), if available and valid.
231
+
- Respond with the `command=reply`message (the requested reply), if available and valid.
232
232
- Otherwise do not reply.
233
233
234
234
### Protocol: Client
@@ -249,8 +249,8 @@ See also:
249
249
250
250
Grid repair is triggered when a replica discovers a corrupt (or missing) grid block.
251
251
252
-
1. The repairing replica sends a `command=request_blocks` to any other replica. The message body contains a list of block `address`/`checksum`s.
253
-
2. Upon receiving a `command=request_blocks`, a replica reads its own grid to check for the requested blocks. For each matching block found, reply with the `command=block` message (the block itself).
252
+
1. The repairing replica sends a `command=get_blocks` to any other replica. The message body contains a list of block `address`/`checksum`s.
253
+
2. Upon receiving a `command=get_blocks`, a replica reads its own grid to check for the requested blocks. For each matching block found, reply with the `command=block` message (the block itself).
254
254
3. Upon receiving a `command=block`, a replica writes the block to its grid, and resolves the reads that were blocked on it.
255
255
256
256
Note that _both sides_ of grid repair can run while the grid is being opened during replica startup.
0 commit comments