Changes between Version 13 and Version 14 of AssignedWork

Timestamp:

Jan 31, 2012, 11:37:59 AM (13 years ago)

Author:

davea

Comment:

--

AssignedWork

@@ -14 +14 @@
 Broadcast jobs are executed exactly once on a given host.
 It the job fails for any reason, it is not retried.
-Broadcast jobs are not handled by a [ValidateIntro validator[
+Broadcast jobs are not handled by a [ValidationIntro validator]
 or [AssimilateIntro assimilator].
 You must develop your own daemon that processes completed broadcast jobs.
 
-To enable broadcast jobs you must add
+To enable broadcast jobs, add
 {{{
 <enable_assignment_multi>1</enable_assignment_multi>
@@ -38 +38 @@
 
  * stop and start the project, or
- * touch the file ''reread_db'' in the project directory
+ * touch the file ''reread_db'' in the project directory.
 
 The '''assign.php''' script (in ops/) lets you manage broadcast jobs.
-It shows a list of broadcast jobs and their status,
-and lets you remove broadcast jobs.
 
 == Targeted jobs ==
@@ -60 +58 @@
 Targeted jobs are validated and assimilated like other jobs.
 They are not replicated; if the job fails on one host in the set,
-it will be retried on another host in the set, and so on until it completes.
+it will be retried on another host in the set, and so on until it completes successfully.
 
-To enable targeted jobs you must add
+To enable targeted jobs, add
 {{{
 <enable_assignment>1</enable_assignment>
@@ -82 +80 @@
 The second way is to transform an existing job into a targeted job.
 This might be done, for example, as part of a system that accelerates
-the completion of batches of jobs by sending the "stragglers" to dedicated hosts.
+the completion of batches of jobs by targeting the "stragglers" to dedicated hosts.
 
-Currently the only way to do this is via a C++ API call,
+Currently this can be done only via a C++ API call,
 and you can only target the job to a user.
 The call is: