TSSP Procedures: Difference between revisions
Jump to navigation
Jump to search
Line 241: | Line 241: | ||
# retry (limit?). exit | # retry (limit?). exit | ||
# undo duration changes to altered allocations. exit | # undo duration changes to altered allocations. exit | ||
# no action. results | # no action. results in skewed channel duration | ||
</td> | </td> | ||
</tr> | </tr> | ||
Line 266: | Line 266: | ||
# retry (limit?). exit | # retry (limit?). exit | ||
# undo resizing of altered allocations. exit | # undo resizing of altered allocations. exit | ||
# no action. results in channel capacity | # no action. results in skewed channel capacity | ||
</td> | </td> | ||
</tr> | </tr> | ||
</table> | </table> |
Revision as of 20:36, 31 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, or desired, to be implemented in parallel. Steps that support parallelism assume that the failure of one of the executing threads compromises the entire operation, triggering aggressive rollback when possible. Inability to rollback can result in several undesired channel states:
- Inaccessible channel capacity (can not be remedied by TSSP)
- Inaccessible channel content (can not be remedied by TSSP)
- Skewed channel duration
- Skewed channel capacity
Step | Occurrence | Parallel (T/F) | Cause of Failure | Procedure |
---|---|---|---|---|
obtain metadata | 5 | F |
|
|
fill channel (store/copy) | 3 | T |
|
|
obtain depot set | 2 | T |
|
|
determine next depot | 2 | F |
|
|
reserve channel (alloc) | 2 | T |
|
|
publish/record metadata | 2 | F |
|
|
order depot set | 1 | F |
|
|
expire channel | 1 | T |
|
|
consume content (load) | 1 | T |
|
|
channel duration | 1 | T |
|
|
channel capacity | 1 | T |
|
|