Changes between Version 22 and Version 23 of GpuWorkFetch

Timestamp:

Jan 1, 2009, 8:07:43 PM (15 years ago)

Author:

jm7

Comment:

--

GpuWorkFetch

@@ -106 +106 @@
  * If P supplies a job for R, D(P,R) is set to true.
  * If we send P a request that doesn't return any jobs, then for each resource R for which req_seconds(R)>0, D(P,R) is set to false.
+     *** Proposed change.  This could be too sensitive to temporary outages - why not have the project respond with information about whether the resource type is currently supported in some other form than the project currently has work.  This would mean a 3 state response - "Work is returned", "No work, but the resource is supported", and "The resource is not supported".
 
 === Per-resource-type backoff ===
@@ -117 +118 @@
 The backoff interval is doubled up to a limit whenever we ask for work of that type and don't get any work;
 it's cleared whenever we get a job of that type.
+
+*** Proposed clarification - the overall contact backoff would be the minimum of the backoff for each resource type.  
+*** Question:  If the project asks for a communications backoff, and one of the resource type backoffs would expire within the project requested backoff, how do we handle that?
+*** Question:  If we need to contact a project for a tasks of two different types, and one of the backoffs is satisfied, do we ask for both types?
 
 === Work-fetch state ===