WIP: New definition of TxID ordered speculative linearizability #6185
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lemmy
reviewed
May 17, 2024
|
|
||
| \* Ordering over txIDs, the form of which is <<view,seqnum>> | ||
| TxIDStrictlyLessThan(x, y) == | ||
| \/ x[1] < y[1] |
There was a problem hiding this comment.
A less invasive refactoring than the introduction of records would be the addition of two definitions such as View==1 and SeqNum==2 to be able to write x[View] < y[View] ....
lemmy
reviewed
May 17, 2024
| \* guarantee provided by CCF. Note that this invariant is stronger than traditional linearizability. | ||
| \* TxID ordered speculative linearizability means that once a rw transaction is committed, it is linearizable | ||
| \* and that the ordering of execution is consistent with the order of transaction IDs. | ||
| \* In CCF, a client receives a response before it learns that the transaction is committed, the speculative |
There was a problem hiding this comment.
If this sentence is grammatically correct, I find it very hard to read.
lemmy
reviewed
May 17, 2024
| \* Note that this invariant is only considers committed read-write transactions. | ||
| CommittedRwOrderedSerializableInv == | ||
| \/ Len(CommittedRwResponses) < 2 | ||
| \/ \A i \in 1..Len(CommittedRwResponses)-1: |
There was a problem hiding this comment.
The first disjunct is redundant because \A i \in 1..0: P is true.
lemmy
reviewed
May 17, 2024
|
|
||
| \* If a transaction response is received (event i) before another transaction is requested (event j), | ||
| \* then tx_id of the first transaction is strictly less than the tx_id of the second transaction. | ||
| \* Note that this invariant is only considers committed read-write transactions. |
lemmy
reviewed
May 17, 2024
| \/ /\ x[1] = y[1] | ||
| /\ x[2] < y[2] | ||
|
|
||
| \* CommittedRwResponseSorted is a subset of history containing only the responses to committed rx transactions |
There was a problem hiding this comment.
- Dangling "Sorted" in "CommittedRwResponseSorted"?
- "subsequence" instead of "subset"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WIP, opened for CI