this repo has no description
Fix headings
+3
-3
+3
-3
internals/overview.md
+3
-3
internals/overview.md
···
63
63
When reads are performed, the keys or key ranges read are tracked interally as read conflicts.
64
64
If and when the transaction is committed, these read conflicts will be used to perform concurrency control.
65
65
66
-
## Performing writes
66
+
### Performing writes
67
67
68
68
Writes are simply buffered internally such that they can be sent when the transaction is committed.
69
69
···
72
72
but in some cases advanced clients may choose to manipulate the write conflicts independently to improve performance or selectively weaken consistency guarantees.
73
73
However, such manipulation is dangerous and not generally recommended.
74
74
75
-
## Committing
75
+
### Committing
76
76
77
77
To commit a transaction, the client gathers up the read version, read conflicts, write conflicts, and writes and sends them to a `CommitBuffer`.
78
78
···
101
101
Once *every* TLog has returned,
102
102
the `CommitBuffer` accordingly returns to all of the clients in the batch.
103
103
104
-
## Storage peeks logs
104
+
### Storage peek
105
105
106
106
Outside of the commit path,
107
107
`Storage` servers "peek" logs for their team by sending peek requests to their corresponding `TLog` servers.