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

auto

parent 11db17a9
No related branches found
No related tags found
No related merge requests found
...@@ -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.
......
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