TSSP Procedures: Difference between revisions

From ReddNet
Jump to navigation Jump to search
Line 19: Line 19:
  <td align=center>F</td>
  <td align=center>F</td>
  <td>
  <td>
# connection timed out
# connection timeout
# authentication failed
# authentication failed
# path not found
# path not found
# permission denied
# permission denied
# connection broken
# connection broken
# transfer canceled
# operation canceled
# client destroyed
# client destroyed
# size mismatch
# size mismatch
Line 45: Line 45:
  <td align=center>3</td>
  <td align=center>3</td>
  <td align=center>T</td>
  <td align=center>T</td>
  <td>-</td>
  <td>
  <td>-</td>
# connection timeout
# authentication failed
# invalid capability
# invalid WRITE key
# insufficient space
# connection broken
# operation canceled
# size mismatch
# input stream closed
</td>
  <td>
# -
# -
# -
# -
# -
# -
# -
# -
# -
</td>
</tr>
</tr>
<tr>
<tr>
Line 53: Line 73:
  <td align=center>T</td>
  <td align=center>T</td>
  <td>
  <td>
# connection timed out
# connection timeout
# authentication failed
# authentication failed
# empty set returned
# empty set returned
# connection broken
# connection broken
# lookup canceled
# operation canceled
# invalid schema
# invalid schema
  </td>
  </td>
Line 88: Line 108:
  <td align=center>2</td>
  <td align=center>2</td>
  <td align=center>T</td>
  <td align=center>T</td>
  <td>-</td>
  <td>
  <td>-</td>
# connection timed out
# authentication failed
# invalid resource
# insufficient capacity
# insufficient duration
# connection broken
# client destroyed
# operation canceled
</td>
  <td>
# -
# -
# -
# -
# -
# -
# -
# -
</td>
</tr>
</tr>
<tr>
<tr>
Line 96: Line 134:
  <td align=center>F</td>
  <td align=center>F</td>
  <td>
  <td>
# connection timed out
# connection timeout
# authentication failed
# authentication failed
# path not found
# path not found
Line 102: Line 140:
# not enough space
# not enough space
# connection broken
# connection broken
# transfer canceled
# operation canceled
# client destroyed
# client destroyed
  </td>
  </td>
Line 133: Line 171:
  <td align=center>1</td>
  <td align=center>1</td>
  <td align=center>T</td>
  <td align=center>T</td>
  <td>-</td>
  <td>
  <td>-</td>
# connection timed out
# authentication failed
# invalid capability
# invalid MANAGE key
# connection broken
# operation canceled
</td>
  <td>
# -
# -
# -
# -
# -
# -
</td>
</tr>
</tr>
<tr>
<tr>
Line 140: Line 192:
  <td align=center>1</td>
  <td align=center>1</td>
  <td align=center>T</td>
  <td align=center>T</td>
  <td>-</td>
  <td>
  <td>-</td>
# connection timed out
# authentication failed
# invalid capability
# invalid READ key
# bytes read mismatch
# connection broken
# operation canceled
# output stream closed
</td>
  <td>
# -
# -
# -
# -
# -
# -
# -
# -
</td>
</tr>
</tr>
<tr>
<tr>

Revision as of 12:12, 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
StepOccurrenceParallel (T/F)Failure TypeProcedure
obtain metadata 5 F
  1. connection timeout
  2. authentication failed
  3. path not found
  4. permission denied
  5. connection broken
  6. operation canceled
  7. client destroyed
  8. size mismatch
  9. invalid schema
  1. -
  2. -
  3. -
  4. -
  5. -
  6. -
  7. -
  8. -
  9. -
fill channel (store/copy) 3 T
  1. connection timeout
  2. authentication failed
  3. invalid capability
  4. invalid WRITE key
  5. insufficient space
  6. connection broken
  7. operation canceled
  8. size mismatch
  9. input stream closed
  1. -
  2. -
  3. -
  4. -
  5. -
  6. -
  7. -
  8. -
  9. -
obtain depot set 2 T
  1. connection timeout
  2. authentication failed
  3. empty set returned
  4. connection broken
  5. operation canceled
  6. invalid schema
  1. -
  2. -
  3. -
  4. -
  5. -
  6. -
determine next depot 2 F
  1. malformed query
  2. invalid schema
  3. null result
  1. -
  2. -
  3. -
reserve channel (alloc) 2 T
  1. connection timed out
  2. authentication failed
  3. invalid resource
  4. insufficient capacity
  5. insufficient duration
  6. connection broken
  7. client destroyed
  8. operation canceled
  1. -
  2. -
  3. -
  4. -
  5. -
  6. -
  7. -
  8. -
publish/record metadata 2 F
  1. connection timeout
  2. authentication failed
  3. path not found
  4. permission denied
  5. not enough space
  6. connection broken
  7. operation canceled
  8. client destroyed
  1. -
  2. -
  3. -
  4. -
  5. -
  6. -
  7. -
  8. -
order depot set 1 F
  1. malformed query
  2. invalid schema
  1. -
  2. -
expire channel 1 T
  1. connection timed out
  2. authentication failed
  3. invalid capability
  4. invalid MANAGE key
  5. connection broken
  6. operation canceled
  1. -
  2. -
  3. -
  4. -
  5. -
  6. -
consume content (load) 1 T
  1. connection timed out
  2. authentication failed
  3. invalid capability
  4. invalid READ key
  5. bytes read mismatch
  6. connection broken
  7. operation canceled
  8. output stream closed
  1. -
  2. -
  3. -
  4. -
  5. -
  6. -
  7. -
  8. -
channel duration 1 T - -
channel capacity 1 T - -
Retrieved from "http://www.reddnet.org/mwiki/index.php?title=TSSP_Procedures&oldid=2968"