Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
C
cmsc818fall2023projects
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Peter Keleher
cmsc818fall2023projects
Commits
b07109b4
Commit
b07109b4
authored
1 year ago
by
Peter J. Keleher
Browse files
Options
Downloads
Patches
Plain Diff
auto
parent
26440eb0
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
notes/ram.md
+4
-4
4 additions, 4 deletions
notes/ram.md
with
4 additions
and
4 deletions
notes/ram.md
+
4
−
4
View file @
b07109b4
...
@@ -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
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment