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
Copy file name to clipboardExpand all lines: content/operate/rs/clusters/optimize/wait.md
+4-6Lines changed: 4 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,19 +35,17 @@ acknowledged within the replica. These are steps 7 and 8.
35
35
36
36
## Blocking write operation on replication
37
37
38
-
With the `WAIT` command, applications can ask to wait for
38
+
With the [`WAIT`]({{<relref "/commands/wait">}}) or [`WAITAOF`]({{<relref "/commands/waitaof">}}) commands, applications can ask to wait for
39
39
acknowledgments only after replication or persistence is confirmed on
40
-
the replica. The flow of a write operation with the WAIT command is:
40
+
the replica. The flow of a write operation with `WAIT` or `WAITAOF` is:
41
41
42
42
1. The application issues a write.
43
43
1. The proxy communicates with the correct primary shard in the system that contains the given key.
44
44
1. Replication communicates the update to the replica shard.
45
-
1.The replica persists the update to disk if the AOF every write setting is selected.
45
+
1.If using `WAITAOF` and the AOF every write setting, the replica persists the update to disk before sending the acknowledgment.
46
46
1. The acknowledgment is sent back from the replica all the way to the proxy with steps 5 to 8.
47
47
48
-
With this flow, the application only gets the acknowledgment from the
49
-
write after durability is achieved with replication to the replica and to
50
-
the persistent storage.
48
+
The application only gets the acknowledgment from the write after durability is achieved with replication to the replica for `WAIT` or `WAITAOF` and to the persistent storage for `WAITAOF` only.
Copy file name to clipboardExpand all lines: content/operate/rs/databases/durability-ha/consistency.md
+4-6Lines changed: 4 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,19 +32,17 @@ Any updates that are issued to the database are typically performed with the fol
32
32
33
33
## Blocking write operation on replication
34
34
35
-
With the `WAIT` command, applications can ask to wait for
35
+
With the [`WAIT`]({{<relref "/commands/wait">}}) or [`WAITAOF`]({{<relref "/commands/waitaof">}}) commands, applications can ask to wait for
36
36
acknowledgments only after replication or persistence is confirmed on
37
-
the replica. The flow of a write operation with the `WAIT`command is:
37
+
the replica. The flow of a write operation with `WAIT`or `WAITAOF` is:
38
38
39
39
1. The application issues a write.
40
40
2. The proxy communicates with the correct primary shard in the system that contains the given key.
41
41
3. Replication communicates the update to the replica shard.
42
-
4.The replica persists the update to disk if the AOF every write setting is selected.
42
+
4.If using `WAITAOF` and the AOF every write setting, the replica persists the update to disk before sending the acknowledgment.
43
43
5. The acknowledgment is sent back from the replica all the way to the proxy with steps 5 to 8.
44
44
45
-
With this flow, the application only gets the acknowledgment from the
46
-
write after durability is achieved with replication to the replica and to
47
-
the persistent storage.
45
+
The application only gets the acknowledgment from the write after durability is achieved with replication to the replica for `WAIT` or `WAITAOF` and to the persistent storage for `WAITAOF` only.
0 commit comments