TSSP Procedures - Revision history

Hunterh: /* Fault Tolerance */

2008-02-01T02:40:55Z

Fault Tolerance

← Older revision		Revision as of 21:40, 31 January 2008
Line 37:		Line 37:
	# exit		# exit
	# no action		# no action
	# retry (limit?)		# retry (limit?). exit
	# exit		# exit
	</td>		</td>
Line 146:		Line 146:
	</td>		</td>
	<td>		<td>
	# retry (limit?). otherwise cache locally(?) or expire channel		# retry (limit?). otherwise cache locally(?) or expire channel. exit
	# cache locally(?) or expire channel		# cache locally(?) or expire channel. exit
	# expire channel		# expire channel. exit
	# expire channel		# expire channel. exit
	# expire channel		# expire channel. exit
	# retry (limit?). otherwise cache locally or expire channel		# retry (limit?). otherwise cache locally or expire channel. exit
	# expire channel		# expire channel. exit
	# no action. results in inaccessible channel capacity and content		# no action. results in inaccessible channel capacity and content
	</td>		</td>
Line 184:		Line 184:
	<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. retry (limit? time?)
	# metadata is not purged, remains in the namespace, and contains unexpired allocations		# metadata is not purged, remains in the namespace, and contains unexpired allocations. exit
	# interpreted as expired allocation. metadata is purged		# interpreted as expired allocation. metadata is purged
	# interpreted as unauthorized allocation. metadata is purged		# interpreted as unauthorized allocation. metadata is purged
	# retry (limit?)		# retry (limit?). exit
	# metadata is not purged, remains in the namespace, and contains unexpired allocations (i.e. partial channel and content)		# metadata is not purged, remains in the namespace, and contains unexpired allocations (i.e. partial channel and content). exit
	# no action. can result in partial channel and content		# no action. can result in partial channel and content
	</td>		</td>

Hunterh: /* Fault Tolerance */

2008-02-01T02:36:26Z

Fault Tolerance

← Older revision		Revision as of 21:36, 31 January 2008
Line 241:		Line 241:
	# retry (limit?). exit		# retry (limit?). exit
	# undo duration changes to altered allocations. exit		# undo duration changes to altered allocations. exit
	# no action. results is channel duration ~~skew~~		# no action. results in skewed channel duration
	</td>		</td>
	</tr>		</tr>
Line 266:		Line 266:
	# retry (limit?). exit		# retry (limit?). exit
	# undo resizing of altered allocations. exit		# undo resizing of altered allocations. exit
	# no action. results in channel capacity ~~skew~~		# no action. results in skewed channel capacity
	</td>		</td>
	</tr>		</tr>
	</table>		</table>

Hunterh: /* Fault Tolerance */

2008-02-01T02:34:57Z

Fault Tolerance

← Older revision		Revision as of 21:34, 31 January 2008
Line 180:		Line 180:
	# connection broken		# connection broken
	# operation canceled		# operation canceled
	# operation interrupted		# operation interrupted (client crash)
	</td>		</td>
	<td>		<td>
Line 204:		Line 204:
	# connection broken		# connection broken
	# operation canceled		# operation canceled
	# operation interrupted		# operation interrupted (client crash)
	# output stream closed		# output stream closed
	</td>		</td>
	<td>		<td>
	# -		# retry. try replica. exit
	# -		# exit
	# -		# try replica. exit
	# -		# try replica. exit
	# -		# retry. try replica. exit
	# -		# retry. try replica. exit
	# -		# exit
	# -		# no action
	# -		# exit
	</td>		</td>
	</tr>		</tr>
Line 231:		Line 231:
	# connection broken		# connection broken
	# operation canceled		# operation canceled
	# operation interrupted		# operation interrupted (client crash)
	</td>		</td>
	<td>		<td>
	# -		# retry (limit?). exit
	# -		# exit
	# -		# exit
	# -		# exit
	# -		# exit
	# -		# retry (limit?). exit
	# -		# undo duration changes to altered allocations. exit
	# -		# no action. results is channel duration skew
	</td>		</td>
	</tr>		</tr>
Line 256:		Line 256:
	# connection broken		# connection broken
	# operation canceled		# operation canceled
	# operation interrupted		# operation interrupted (client crash)
	</td>		</td>
	<td>		<td>
	# -		# retry (limit?). exit
	# -		# exit
	# -		# exit
	# -		# exit
	# -		# exit
	# -		# retry (limit?). exit
	# -		# undo resizing of altered allocations. exit
	# -		# no action. results in channel capacity skew
	</td>		</td>
	</tr>		</tr>
	</table>		</table>

Hunterh: /* Fault Tolerance */

2008-02-01T02:26:33Z

Fault Tolerance

← Older revision		Revision as of 21:26, 31 January 2008
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>

Hunterh: /* Fault Tolerance */

2008-02-01T02:12:09Z

Fault Tolerance

← Older revision		Revision as of 21:12, 31 January 2008
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>
	# -		#
	# -		# -
	# -		# -

Hunterh: /* Fault Tolerance */

2008-02-01T00:59:49Z

Fault Tolerance

← Older revision		Revision as of 19:59, 31 January 2008
Line 30:		Line 30:
	</td>		</td>
	<td>		<td>
	# ~~desist~~		# exit
	# ~~desist~~		# exit
	# ~~desist~~		# exit
	# ~~desist~~		# exit
	# ~~desist~~		# exit
	# ~~desist~~		# exit
	# retry (limit?)		# retry (limit?)
	# retry (limit?)		# retry (limit?)
	# ~~desist~~		# exit
	</td>		</td>
	</tr>		</tr>
Line 58:		Line 58:
	</td>		</td>
	<td>		<td>
	# try next depot/resource if available. otherwise ~~desist~~		# try next depot/resource if available. otherwise, decrement successful allocations, purge metadata, and exit
	# try next depot/resource if available. otherwise ~~desist~~		# try next depot/resource if available. otherwise, decrement successful allocations, purge metadata, and exit
	# redo allocate		# redo allocate
	# redo allocate		# redo allocate
	# try next depot/resource if available. otherwise ~~desist~~		# try next depot/resource if available. otherwise, decrement successful allocations, purge metadata, and exit
	# retry (limit?)		# retry (limit?). otherwise, decrement successful allocations, purge metadata, and exit
	# ~~desist~~		# decrement successful allocations, purge metadata, and exit
	# retry (limit?)		# retry (limit?). otherwise, decrement successful allocations, purge metadata, and exit
	# ~~desist~~		# decrement successful allocations, purge metadata, and exit
	# ~~desist~~		# decrement successful allocations, purge metadata, and exit
	</td>		</td>
	</tr>		</tr>
Line 83:		Line 83:
	</td>		</td>
	<td>		<td>
	# -		# exit
	# -		# exit
	# -		# exit (=non-existant resource)
	# -		# retry (limit?). otherwise, exit
	# -		# exit
	# -		# exit
	</td>		</td>
	</tr>		</tr>
Line 101:		Line 101:
	</td>		</td>
	<td>		<td>
	# -		# exit
	# -		# exit
	# -		# exit
	</td>		</td>
	</tr>		</tr>

Hunterh: /* Fault Tolerance */

2008-02-01T00:47:52Z

Fault Tolerance

← Older revision		Revision as of 19:47, 31 January 2008
Line 30:		Line 30:
	</td>		</td>
	<td>		<td>
	# -		# desist
	# -		# desist
	# -		# desist
	# -		# desist
	# -		# desist
	# -		# desist
	# -		# retry (limit?)
	# -		# retry (limit?)
	# -		# desist
	</td>		</td>
	</tr>		</tr>
Line 58:		Line 58:
	</td>		</td>
	<td>		<td>
	# -		# try next depot/resource if available. otherwise desist
	# -		# try next depot/resource if available. otherwise desist
	# -		# redo allocate
	# -		# redo allocate
	# -		# try next depot/resource if available. otherwise desist
	# -		# retry (limit?)
	# -		# desist
	# -		# retry (limit?)
	# -		# desist
	# -		# desist
	</td>		</td>
	</tr>		</tr>

Hunterh: /* Fault Tolerance */

2008-01-16T13:20:23Z

Fault Tolerance

← Older revision		Revision as of 08:20, 16 January 2008
Line 4:		Line 4:

	= Fault Tolerance =		= 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:		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 capacity (can not be remedied by TSSP)
	* Inaccessible channel content (can not be remedied by TSSP)		* Inaccessible channel content (can not be remedied by TSSP)

Hunterh: /* Fault Tolerance */

2008-01-03T17:30:56Z

Fault Tolerance

← Older revision		Revision as of 12:30, 3 January 2008
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>

Hunterh: /* Fault Tolerance */

2008-01-03T17:29:22Z

Fault Tolerance

← Older revision		Revision as of 12:29, 3 January 2008
Line 5:		Line 5:
	= Fault Tolerance =		= 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:		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 capacity (can not be remedied by TSSP)
	* Inaccessible channel content		* Inaccessible channel content (can not be remedied by TSSP)
	* Skewed channel duration		* Skewed channel duration
	* Skewed channel capacity		* Skewed channel capacity