TSSP Procedures: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 4: | Line 4: | ||
= Fault Tolerance = | = Fault Tolerance = | ||
The steps that compose the five proposed standard operations are shown ranked by how many times they appear in the operations' construction. Also, each step is categorized as being able to be implemented in parallel. Those that support parallelism assume that the failure of one of the executing threads compromises the entire operation, triggering aggressive rollback when possible. | |||
<table border=1> | <table border=1> |
Revision as of 09:36, 3 January 2008
This section contains recommendations pertaining to the Issues section of the TSSP Framework article.
(back to Protocol Standardization Efforts)
Fault Tolerance
The steps that compose the five proposed standard operations are shown ranked by how many times they appear in the operations' construction. Also, each step is categorized as being able to be implemented in parallel. Those that support parallelism assume that the failure of one of the executing threads compromises the entire operation, triggering aggressive rollback when possible.
Step | Occurrence | Parallel (T/F) | Failure Type | Procedure |
---|---|---|---|---|
obtain metadata | 5 | F |
|
|
fill channel | 3 | T | - | - |
obtain depot set | 2 | T |
|
|
determine next depot | 2 | F |
|
|
reserve channel | 2 | T | - | - |
publish/record metadata | 2 | F |
|
|
order depot set | 1 | F |
|
|
expire channel | 1 | T | - | - |
consume content | 1 | T | - | - |
channel duration | 1 | T | - | - |
channel capacity | 1 | T | - | - |