The batch process is not started up automatically
Bug #910927 reported by
Jean-Paul Calderone
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Divmod Axiom |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
This was filed in the old Divmod issue tracker as ticket 2963.
When axiomatic starts up, it does nothing special with the batch processing system. If application code explicitly requests something from the remote batch processor, the batch process will get started up. However, if there are pending items in need of remote processing, these will not cause the batch process to start (so the items are not processed). And the creation of new items for remote processing is also not sufficient to start the process.
This is hard to fix for real, but an improvement is to at least start the batch process when new items for remote processing are created.
Related branches
lp:~divmod-dev/divmod.org/batch-process-start-heuristic-2963
- Tristan Seligmann: Approve
-
Diff: 272 lines (+174/-3)3 files modifiedAxiom/axiom/batch.py (+43/-3)
Axiom/axiom/iaxiom.py (+10/-0)
Axiom/axiom/test/test_batch.py (+121/-0)
Changed in divmod-axiom: | |
status: | New → Fix Committed |
Changed in divmod-axiom: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.