TSSP Procedures: Difference between revisions

From ReddNet
Jump to navigation Jump to search
Line 58: Line 58:
  </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, expire channel, 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, expire channel, purge metadata, and exit
# redo allocate
# redo allocate
# redo allocate
# redo allocate
# try next depot/resource if available. otherwise, execute channel teardown, purge metadata, and exit
# try next depot/resource if available. otherwise, expire channel, purge metadata, and exit
# retry (limit?). otherwise, decrement successful allocations, purge metadata, and exit
# retry (limit?). otherwise, expire channel, purge metadata, and exit
# decrement successful allocations, 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
# decrement successful allocations, purge metadata, and exit
# expire channel, purge metadata, and exit
# decrement successful allocations, 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, execute channel teardown, purge metadata, and exit
# try next depot/resource if available. otherwise, expire channel, 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, expire channel, 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, expire channel, 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, expire channel, 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, expire channel, 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, 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 execute channel teardown
# retry (limit?). otherwise cache locally(?) or expire channel
# cache locally(?) or execute channel teardown
# cache locally(?) or expire channel
# execute channel teardown
# expire channel
# execute channel teardown
# expire channel
# execute channel teardown
# expire channel
# retry (limit?). otherwise cache locally or execute channel teardown
# retry (limit?). otherwise cache locally or expire channel
# execute channel teardown
# 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 21: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
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, expire channel, purge metadata, and exit
  2. try next depot/resource if available. otherwise, expire channel, purge metadata, and exit
  3. redo allocate
  4. redo allocate
  5. try next depot/resource if available. otherwise, expire channel, purge metadata, and exit
  6. retry (limit?). otherwise, expire channel, purge metadata, and exit
  7. expire channel, purge metadata, and exit
  8. no action. results in inaccessible channel capacity and content
  9. expire channel, purge metadata, and exit
  10. expire channel, 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 (client crash)
  1. try next depot/resource if available. otherwise, expire channel, purge metadata, and exit
  2. try next depot/resource if available. otherwise, expire channel, purge metadata, and exit
  3. try next depot/resource if available. otherwise, expire channel, purge metadata, and exit
  4. try next depot/resource if available. otherwise, expire channel, purge metadata, and exit
  5. try next depot/resource if available. otherwise, expire channel, purge metadata, and exit
  6. try next depot/resource if available. otherwise, expire channel, 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 expire channel
  2. cache locally(?) or expire channel
  3. expire channel
  4. expire channel
  5. expire channel
  6. retry (limit?). otherwise cache locally or expire channel
  7. expire channel
  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. metadata is not purged, remains in the namespace, and contains unexpired allocations. retry (limit? time?)
  2. metadata is not purged, remains in the namespace, and contains unexpired allocations
  3. interpreted as expired allocation. metadata is purged
  4. interpreted as unauthorized allocation. metadata is purged
  5. retry (limit?)
  6. metadata is not purged, remains in the namespace, and contains unexpired allocations (i.e. partial channel and content)
  7. no action. can result in partial channel and content
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. -