TSSP Procedures: Difference between revisions

From ReddNet
Jump to navigation Jump to search
Line 25: Line 25:
# connection broken
# connection broken
# operation canceled
# operation canceled
# operation interrupted
# operation interrupted (client crash)
# size mismatch
# size mismatch
# invalid schema
# invalid schema
Line 36: Line 36:
# exit
# exit
# exit
# exit
# retry (limit?)
# no action
# retry (limit?)
# retry (limit?)
# exit
# exit
Line 53: Line 53:
# connection broken
# connection broken
# operation canceled
# operation canceled
# operation interrupted
# operation interrupted (client crash)
# size mismatch
# size mismatch
# input stream closed
# input stream closed
  </td>
  </td>
  <td>
  <td>
# try next depot/resource if available. otherwise, decrement successful allocations, purge metadata, and exit
# try next depot/resource if available. otherwise, execute channel teardown, purge metadata, and exit
# try next depot/resource if available. otherwise, decrement successful allocations, purge metadata, and exit
# try next depot/resource if available. otherwise, execute channel teardown, purge metadata, and exit
# redo allocate
# redo allocate
# redo allocate
# redo allocate
# try next depot/resource if available. otherwise, decrement successful allocations, purge metadata, and exit
# try next depot/resource if available. otherwise, execute channel teardown, purge metadata, and exit
# retry (limit?). otherwise, decrement successful allocations, purge metadata, and exit
# retry (limit?). otherwise, decrement successful allocations, purge metadata, and exit
# decrement successful allocations, purge metadata, and exit
# decrement successful allocations, purge metadata, and exit
# retry (limit?). otherwise, decrement successful allocations, purge metadata, and exit
# no action. results in inaccessible channel capacity and content
# decrement successful allocations, purge metadata, and exit
# decrement successful allocations, purge metadata, and exit
# decrement successful allocations, purge metadata, and exit
# decrement successful allocations, purge metadata, and exit
Line 77: Line 77:
# connection timeout
# connection timeout
# authentication failed
# authentication failed
# empty set returned
# empty set returned (i.e. non-existent resource)
# connection broken
# connection broken
# operation canceled
# operation canceled
Line 85: Line 85:
# exit
# exit
# exit
# exit
# exit (=non-existant resource)
# exit  
# retry (limit?). otherwise, exit
# retry (limit?). otherwise, exit
# exit
# exit
Line 121: Line 121:
  </td>
  </td>
  <td>
  <td>
# -
# try next depot/resource if available. otherwise, execute channel teardown, purge metadata, and exit
# -
# try next depot/resource if available. otherwise, execute channel teardown, purge metadata, and exit
# -
# try next depot/resource if available. otherwise, execute channel teardown, purge metadata, and exit
# -
# try next depot/resource if available. otherwise, execute channel teardown, purge metadata, and exit
# -
# try next depot/resource if available. otherwise, execute channel teardown, purge metadata, and exit
# -
# try next depot/resource if available. otherwise, execute channel teardown, purge metadata, and exit
# -
# exit
# -
# no action. results in inaccessible channel capacity
  </td>
  </td>
</tr>
</tr>
Line 143: Line 143:
# connection broken
# connection broken
# operation canceled
# operation canceled
# operation interrupted
# operation interrupted (client crash)
  </td>
  </td>
  <td>
  <td>
# -
# retry (limit?). otherwise cache locally(?) or execute channel teardown
# -
# cache locally(?) or execute channel teardown
# -
# execute channel teardown
# -
# execute channel teardown
# -
# execute channel teardown
# -
# retry (limit?). otherwise cache locally or execute channel teardown
# -
# execute channel teardown
# -
# no action. results in inaccessible channel capacity and content
  </td>
  </td>
</tr>
</tr>
Line 165: Line 165:
  </td>
  </td>
  <td>
  <td>
# -
# exit
# -
# exit
  </td>
  </td>
</tr>
</tr>
Line 183: Line 183:
  </td>
  </td>
  <td>
  <td>
# -
#  
# -
# -
# -
# -

Revision as of 21:12, 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
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 (client crash)
  8. size mismatch
  9. invalid schema
  1. exit
  2. exit
  3. exit
  4. exit
  5. exit
  6. exit
  7. no action
  8. retry (limit?)
  9. exit
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 (client crash)
  9. size mismatch
  10. input stream closed
  1. try next depot/resource if available. otherwise, execute channel teardown, purge metadata, and exit
  2. try next depot/resource if available. otherwise, execute channel teardown, purge metadata, and exit
  3. redo allocate
  4. redo allocate
  5. try next depot/resource if available. otherwise, execute channel teardown, purge metadata, and exit
  6. retry (limit?). otherwise, decrement successful allocations, purge metadata, and exit
  7. decrement successful allocations, purge metadata, and exit
  8. no action. results in inaccessible channel capacity and content
  9. decrement successful allocations, purge metadata, and exit
  10. decrement successful allocations, purge metadata, and exit
obtain depot set 2 T
  1. connection timeout
  2. authentication failed
  3. empty set returned (i.e. non-existent resource)
  4. connection broken
  5. operation canceled
  6. invalid schema
  1. exit
  2. exit
  3. exit
  4. retry (limit?). otherwise, exit
  5. exit
  6. exit
determine next depot 2 F
  1. malformed query
  2. invalid schema
  3. null result
  1. exit
  2. exit
  3. exit
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. try next depot/resource if available. otherwise, execute channel teardown, purge metadata, and exit
  2. try next depot/resource if available. otherwise, execute channel teardown, purge metadata, and exit
  3. try next depot/resource if available. otherwise, execute channel teardown, purge metadata, and exit
  4. try next depot/resource if available. otherwise, execute channel teardown, purge metadata, and exit
  5. try next depot/resource if available. otherwise, execute channel teardown, purge metadata, and exit
  6. try next depot/resource if available. otherwise, execute channel teardown, purge metadata, and exit
  7. exit
  8. no action. results in inaccessible channel capacity
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 (client crash)
  1. retry (limit?). otherwise cache locally(?) or execute channel teardown
  2. cache locally(?) or execute channel teardown
  3. execute channel teardown
  4. execute channel teardown
  5. execute channel teardown
  6. retry (limit?). otherwise cache locally or execute channel teardown
  7. execute channel teardown
  8. no action. results in inaccessible channel capacity and content
order depot set 1 F
  1. malformed query
  2. invalid schema
  1. exit
  2. exit
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. -
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. -