TSSP Procedures

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	connection timed out authentication failed path not found permission denied connection broken transfer canceled client destroyed size mismatch invalid schema	- - - - - - - - -
fill channel (store/copy)	3	T	-	-
obtain depot set	2	T	connection timed out authentication failed empty set returned connection broken lookup canceled invalid schema	- - - - - -
determine next depot	2	F	malformed query invalid schema null result	- - -
reserve channel (alloc)	2	T	-	-
publish/record metadata	2	F	connection timed out authentication failed path not found permission denied not enough space connection broken transfer canceled client destroyed	- - - - - - - -
order depot set	1	F	malformed query invalid schema	- -
expire channel	1	T	-	-
consume content (load)	1	T	-	-
channel duration	1	T	-	-
channel capacity	1	T	-	-