#197 closed enhancement (done)
Use SQLite backend to store waiting engines and results instead of in-memory dictionaries
Reported by: | gkronber | Owned by: | gkronber |
---|---|---|---|
Priority: | low | Milestone: | HeuristicLab 3.3.0 |
Component: | ZZZ OBSOLETE: Grid | Version: | 3.1 |
Keywords: | Cc: |
Description
Change History (11)
comment:1 Changed 16 years ago by gkronber
- Status changed from new to assigned
comment:2 Changed 16 years ago by gkronber
comment:3 Changed 16 years ago by gkronber
Next step: remove the wait-handle list. The server can be stopped and restarted with the DB backend. Wait-handles are not a good fit for this design. It would probably better to go back to polling results from the distributed engine. With a kind of polling operator it would also be possible to persist the distributed engine while jobs are running on the grid and later resume the engine.
comment:4 Changed 16 years ago by gkronber
removed the wait-handles from the engine-store with r501
comment:5 Changed 16 years ago by gkronber
reenabled waiting/running/finished counters with r504
comment:6 Changed 16 years ago by gkronber
improved DB performance by reducing the I/O load with an improved select statement with r505
comment:7 Changed 16 years ago by gkronber
fixed race-conditions with r505:507
comment:8 Changed 16 years ago by gkronber
- Resolution set to fixed
- Status changed from assigned to closed
The DB backend seems to work nicely. Expiry of old jobs doesn't work yet however this is covered in the follow up ticket #251). Closing this ticket for now.
comment:9 Changed 16 years ago by swagner
- Milestone changed from 3.1 to Iteration 0
Milestone 3.1 deleted
comment:10 Changed 14 years ago by swagner
- Milestone changed from Iteration 0 to Current
Milestone Iteration 0 deleted
comment:11 Changed 14 years ago by swagner
- Milestone changed from Current to HeuristicLab 3.3.0
Milestone Current deleted
added basic DB backend with r500