Niclas: Thanks! I checked in the patches. The one about setting batch state to COMPLETE I did in a slightly different way: set batch.state to IN_PROGRESS only after its workunits have been created, and set its state to COMPLETED only if its state is currently IN_PROGRESS (not INIT). Let me know if this looks OK.
I updated the doc for "inline" file mode: http://boinc.berkeley.edu/trac/wiki/RemoteJobs -- David On 19-Jun-2013 3:09 AM, Niclas Lockner wrote:
Hi, I have attached some patches that might be of interest. In the software we use to submit jobs to the Boinc server, the submit is done and then a monitor is started that monitors the state of the submitted batches. When the Boinc server is under heavy load, say hundreds of submits under a short time, the monitors sometimes start to query the batches before the workunits have been written to the Boinc server's database. In those cases, the get_batch_params in submit_util.inc sets the state of the batch to complete when a batch is queried. I have fixed this in one of the attached patches. It doesn't exist a case when the state should be set to complete when the batch has no WUs, right? We also needed to query the available applications so I extended apps.php to support that. In the attached patch I've added the applications' names to the returned XML, but note that the name element now contains the actual name and not the user-friendly name, so depending on how apps.php is currently used the patch may break things. If that is the case then maybe you could name the elements name and name_short or something. We also send our files' contents inline when submitting jobs. Maybe that possibility is interesting to others as well. /Niclas Lockner
_______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
