TSSP Procedures: Difference between revisions
Jump to navigation
Jump to search
Line 58: | Line 58: | ||
</td> | </td> | ||
<td> | <td> | ||
# try next depot/resource if available. otherwise, | # try next depot/resource if available. otherwise, expire channel, purge metadata, and exit | ||
# try next depot/resource if available. otherwise, | # try next depot/resource if available. otherwise, expire channel, purge metadata, and exit | ||
# redo allocate | # redo allocate | ||
# redo allocate | # redo allocate | ||
# try next depot/resource if available. otherwise, | # try next depot/resource if available. otherwise, expire channel, purge metadata, and exit | ||
# retry (limit?). otherwise, | # retry (limit?). otherwise, expire channel, purge metadata, and exit | ||
# | # expire channel, purge metadata, and exit | ||
# no action. results in inaccessible channel capacity and content | # no action. results in inaccessible channel capacity and content | ||
# | # expire channel, purge metadata, and exit | ||
# | # expire channel, purge metadata, and exit | ||
</td> | </td> | ||
</tr> | </tr> | ||
Line 118: | Line 118: | ||
# connection broken | # connection broken | ||
# operation canceled | # operation canceled | ||
# operation interrupted | # operation interrupted (client crash) | ||
</td> | </td> | ||
<td> | <td> | ||
# try next depot/resource if available. otherwise, | # try next depot/resource if available. otherwise, expire channel, purge metadata, and exit | ||
# try next depot/resource if available. otherwise, | # try next depot/resource if available. otherwise, expire channel, purge metadata, and exit | ||
# try next depot/resource if available. otherwise, | # try next depot/resource if available. otherwise, expire channel, purge metadata, and exit | ||
# try next depot/resource if available. otherwise, | # try next depot/resource if available. otherwise, expire channel, purge metadata, and exit | ||
# try next depot/resource if available. otherwise, | # try next depot/resource if available. otherwise, expire channel, purge metadata, and exit | ||
# try next depot/resource if available. otherwise, | # try next depot/resource if available. otherwise, expire channel, purge metadata, and exit | ||
# exit | # exit | ||
# no action. results in inaccessible channel capacity | # no action. results in inaccessible channel capacity | ||
Line 146: | Line 146: | ||
</td> | </td> | ||
<td> | <td> | ||
# retry (limit?). otherwise cache locally(?) or | # retry (limit?). otherwise cache locally(?) or expire channel | ||
# cache locally(?) or | # cache locally(?) or expire channel | ||
# | # expire channel | ||
# | # expire channel | ||
# | # expire channel | ||
# retry (limit?). otherwise cache locally or | # retry (limit?). otherwise cache locally or expire channel | ||
# | # expire channel | ||
# no action. results in inaccessible channel capacity and content | # no action. results in inaccessible channel capacity and content | ||
</td> | </td> | ||
Line 183: | Line 183: | ||
</td> | </td> | ||
<td> | <td> | ||
# | # metadata is not purged, remains in the namespace, and contains unexpired allocations. retry (limit? time?) | ||
# | # metadata is not purged, remains in the namespace, and contains unexpired allocations | ||
# | # interpreted as expired allocation. metadata is purged | ||
# | # interpreted as unauthorized allocation. metadata is purged | ||
# | # retry (limit?) | ||
# | # metadata is not purged, remains in the namespace, and contains unexpired allocations (i.e. partial channel and content) | ||
# | # no action. can result in partial channel and content | ||
</td> | </td> | ||
</tr> | </tr> |
Revision as of 20:26, 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 |
|
|