#2 closed feature request (rejected)
'Stop' functionality for distributed engines.
| Reported by: | gkronber | Owned by: | gkronber |
|---|---|---|---|
| Priority: | lowest | Milestone: | HeuristicLab 3.3.0 |
| Component: | ZZZ OBSOLETE: DistributedEngine | Version: | 3.2 |
| Keywords: | Cc: |
Description
Change History (12)
comment:1 Changed 17 years ago by gkronber
- Status changed from new to assigned
comment:2 Changed 17 years ago by gkronber
- Milestone changed from 3.0 to 3.1
- Owner gkronber deleted
- Status changed from assigned to new
- Version changed from 3.0 to 3.1
comment:3 Changed 17 years ago by gkronber
- Owner set to gkronber
comment:4 Changed 17 years ago by gkronber
After changes related to #149. Hitting the stop-button has the effect that the engine stops at the next synchronization point. That means if there is a distributed operation in progress it waits until all results are received to continue operation and stops at the next possible local operation.
A possible improvement would be to immediately stop the engine (without stopping the distributed jobs and without waiting for the results). Meaning the grid will continue to work on the already submitted jobs. If the user decides to continue operation it would be possible to check the server for already running/finished jobs of the parallel execution and resume with the results-gathering stage instead of resubmitting the same jobs to the server.
comment:5 Changed 16 years ago by gkronber
- Priority changed from major to minor
comment:6 Changed 16 years ago by gkronber
- Milestone changed from 3.1 to 3.2
- Version changed from 3.1 to 3.2
comment:7 Changed 16 years ago by gkronber
not high priority since distributed computing project is currently building a better framework for this.
comment:8 Changed 16 years ago by gkronber
- Priority changed from minor to trivial
comment:9 Changed 16 years ago by swagner
- Milestone changed from 3.2 to Iteration 0
Milestone 3.2 deleted
comment:10 Changed 15 years ago by gkronber
- Resolution set to wontfix
- Status changed from new to closed
comment:11 Changed 14 years ago by swagner
- Milestone changed from Iteration 4 to Current
Milestone Iteration 4 deleted
comment:11 Changed 14 years ago by swagner
- Milestone changed from Current to HeuristicLab 3.3.0
Milestone Current deleted
This ticket is finished partially in HL 3.0. Stop works but when resuming the engine executes remaining operations locally until the next parallel composite operation is encountered. However this is not a high priority for HL 3.0 so I'm moving this ticket to milestone HL 3.1.