Worker-side job status check should not use the database
Bug #882423 reported by
Muharem Hrnjadovic
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenQuake (deprecated) |
Won't Fix
|
High
|
Unassigned |
Bug Description
Presently Job.is_
postgres database.
This introduces a new and unnecessary dependency. The job status
check should be based on data in the redis key-value-store instead.
Changed in openquake: | |
status: | New → Confirmed |
importance: | Undecided → High |
milestone: | none → 0.4.5 |
Changed in openquake: | |
milestone: | 0.4.5 → 0.4.6 |
Changed in openquake: | |
milestone: | 0.4.6 → 0.5.1 |
Changed in openquake: | |
milestone: | 0.5.1 → none |
tags: | added: database |
To post a comment you must log in.
The `check_job_status` function which calls this bit of code is everywhere in our task code; it's called as the first statement of each task. We should consider refactoring `check_job_status` as a decorator to make things cleaner.