Skip to content
Snippets Groups Projects
Commit b07109b4 authored by Peter J. Keleher's avatar Peter J. Keleher
Browse files

auto

parent 26440eb0
No related branches found
No related tags found
No related merge requests found
...@@ -227,20 +227,20 @@ When received by server: ...@@ -227,20 +227,20 @@ When received by server:
- `prepare` (version/lock checks) - `prepare` (version/lock checks)
- `decision` (this phase in background, client already notified) - `decision` (this phase in background, client already notified)
("the transaction is effectively committed once a durable lock record has been written for each of the objects") ("the transaction is effectively committed once a durable lock record has been written for each of the objects")
- **strict serializability** using **optimistic cc**
- updates deferred until commit request - updates deferred until commit request
- reads executed normally, *versions recorded* - reads executed normally, *versions recorded*
- writes on commit phase, possibly w/ expected version - writes on commit phase, possibly w/ expected version
- commit is two-phase
- fail *if version-check fails, or locked by another transaction* - fail *if version-check fails, or locked by another transaction*
- **decision** RPCs in background
- fast case - fast case
- *single server* owns all objects in transaction - *single server* owns all objects in transaction
- *read-only*, even in distributed case only a single round - *read-only*, even in distributed case only a single round
- on client crash, recovery coordinator finishes, hoping to abort unless already committed - on client crash, recovery coordinator finishes, hoping to abort unless already committed
## Issues ## Issues
- worried that storing completion records will not scale well - background decision RPCs imply longer lock holding
- local operation
- either disk or (for RAMCloud) replicating elsewhere
- why optional version checking in transactions? (atomic operation primitive)
## Questions/comments ## Questions/comments
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment