TSSP Procedures: Difference between revisions

From ReddNet
Jump to navigation Jump to search
Line 12: Line 12:
<table border=1>
<table border=1>
<tr>
<tr>
<th>Step</th><th>Occurrence</th><th>Parallel (T/F)</th><th>Failure Type</th><th>Procedure</th>
<th>Step</th><th>Occurrence</th><th>Parallel (T/F)</th><th>Cause of Failure</th><th>Procedure</th>
</tr>
</tr>
  <tr>
  <tr>

Revision as of 12:30, 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 (can not be remedied by TSSP)
  • Inaccessible channel content (can not be remedied by TSSP)
  • Skewed channel duration
  • Skewed channel capacity
StepOccurrenceParallel (T/F)Cause of FailureProcedure
obtain metadata 5 F
  1. connection timeout
  2. authentication failed
  3. path not found
  4. permission denied
  5. connection broken
  6. operation canceled
  7. operation interrupted
  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. operation interrupted
  9. size mismatch
  10. input stream closed
  1. -
  2. -
  3. -
  4. -
  5. -
  6. -
  7. -
  8. -
  9. -
  10. -
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. operation canceled
  8. operation interrupted
  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. operation interrupted
  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
  7. operation interrupted
  1. -
  2. -
  3. -
  4. -
  5. -
  6. -
  7. -
consume content (load) 1 T
  1. connection timed out
  2. authentication failed
  3. invalid capability
  4. invalid READ key
  5. size mismatch
  6. connection broken
  7. operation canceled
  8. operation interrupted
  9. output stream closed
  1. -
  2. -
  3. -
  4. -
  5. -
  6. -
  7. -
  8. -
  9. -
channel duration 1 T
  1. connection timed out
  2. authentication failed
  3. invalid capability
  4. invalid MANAGE key
  5. insufficient duration
  6. connection broken
  7. operation canceled
  8. operation interrupted
  1. -
  2. -
  3. -
  4. -
  5. -
  6. -
  7. -
  8. -
channel capacity 1 T
  1. connection timed out
  2. authentication failed
  3. invalid capability
  4. invalid MANAGE key
  5. insufficient capacity
  6. connection broken
  7. operation canceled
  8. operation interrupted
  1. -
  2. -
  3. -
  4. -
  5. -
  6. -
  7. -
  8. -