TSSP Procedures: Difference between revisions
Jump to navigation
Jump to search
Line 25: | Line 25: | ||
# connection broken | # connection broken | ||
# operation canceled | # operation canceled | ||
# | # operation interrupted | ||
# size mismatch | # size mismatch | ||
# invalid schema | # invalid schema | ||
Line 53: | Line 53: | ||
# connection broken | # connection broken | ||
# operation canceled | # operation canceled | ||
# operation interrupted | |||
# size mismatch | # size mismatch | ||
# input stream closed | # input stream closed | ||
</td> | </td> | ||
<td> | <td> | ||
# - | |||
# - | # - | ||
# - | # - | ||
Line 115: | Line 117: | ||
# insufficient duration | # insufficient duration | ||
# connection broken | # connection broken | ||
# operation canceled | # operation canceled | ||
# operation interrupted | |||
</td> | </td> | ||
<td> | <td> | ||
Line 141: | Line 143: | ||
# connection broken | # connection broken | ||
# operation canceled | # operation canceled | ||
# | # operation interrupted | ||
</td> | </td> | ||
<td> | <td> | ||
Line 178: | Line 180: | ||
# connection broken | # connection broken | ||
# operation canceled | # operation canceled | ||
# operation interrupted | |||
</td> | </td> | ||
<td> | <td> | ||
# - | |||
# - | # - | ||
# - | # - | ||
Line 197: | Line 201: | ||
# invalid capability | # invalid capability | ||
# invalid READ key | # invalid READ key | ||
# | # size mismatch | ||
# connection broken | # connection broken | ||
# operation canceled | # operation canceled | ||
# operation interrupted | |||
# output stream closed | # output stream closed | ||
</td> | </td> | ||
<td> | <td> | ||
# - | |||
# - | # - | ||
# - | # - | ||
Line 217: | Line 223: | ||
<td align=center>1</td> | <td align=center>1</td> | ||
<td align=center>T</td> | <td align=center>T</td> | ||
<td> | <td> | ||
<td>-</td> | # connection timed out | ||
# authentication failed | |||
# invalid capability | |||
# invalid MANAGE key | |||
# insufficient duration | |||
# connection broken | |||
# operation canceled | |||
# operation interrupted | |||
</td> | |||
<td> | |||
# - | |||
# - | |||
# - | |||
# - | |||
# - | |||
# - | |||
# - | |||
# - | |||
</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 224: | Line 248: | ||
<td align=center>1</td> | <td align=center>1</td> | ||
<td align=center>T</td> | <td align=center>T</td> | ||
<td> | <td> | ||
<td>-</td> | # connection timed out | ||
# authentication failed | |||
# invalid capability | |||
# invalid MANAGE key | |||
# insufficient capacity | |||
# connection broken | |||
# operation canceled | |||
# operation interrupted | |||
</td> | |||
<td> | |||
# - | |||
# - | |||
# - | |||
# - | |||
# - | |||
# - | |||
# - | |||
# - | |||
</td> | |||
</tr> | </tr> | ||
</table> | </table> |
Revision as of 11:23, 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, 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 states:
- Inaccessible channel capacity
- Inaccessible channel content
- Skewed channel duration
- Skewed channel capacity
Step | Occurrence | Parallel (T/F) | Failure Type | 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 |
|
|