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
c075e2fc
Commit
c075e2fc
authored
1 year ago
by
Peter J. Keleher
Browse files
Options
Downloads
Patches
Plain Diff
auto
parent
11db17a9
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
p6.md
+10
-0
10 additions, 0 deletions
p6.md
with
10 additions
and
0 deletions
p6.md
+
10
−
0
View file @
c075e2fc
...
@@ -159,6 +159,16 @@ only by `Apply()` calls. These calls are immediate for
...
@@ -159,6 +159,16 @@ only by `Apply()` calls. These calls are immediate for
non-transactional updates, but
*
calls for transactional updates are
non-transactional updates, but
*
calls for transactional updates are
delayed until a transaction is known to have committed
*
.
delayed until a transaction is known to have committed
*
.
## Details
-
Start/finish transaction commands should have
*oids*
matching their
*tids*
.
-
Distinct transactions should have distinct
*tids*
.
-
KV and transaction objects should have
*oids*
should be greater than 0, and of
course should be unique across the space of all KV objects and
transactions.
-
The leader election record will have
*oid*
0. It should be treated
the same as any other record by the tango runtime, but will never be
the cause of an
`apply()`
upcall since there are no KV objects w/
*oid*
0.
## Something Else
## Something Else
Build some other distributed data type on tango. Or do something else cool w/ Raft.
Build some other distributed data type on tango. Or do something else cool w/ Raft.
...
...
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