Opened 3 years ago

Last modified 9 months ago

#2561 assigned defect

TimeLimitRun does not work with the Hive Slave

Reported by: ascheibe Owned by: jkarder
Priority: medium Milestone: HeuristicLab 3.3.16
Component: Hive.Client Version:
Keywords: Cc:

Description (last modified by ascheibe)

TimeLimitRun's check-pointing triggers the pause event. The slave registers on this event and then sends the task back to the server.

Change History (6)

comment:1 Changed 3 years ago by ascheibe

  • Description modified (diff)

comment:2 Changed 2 years ago by ascheibe

  • Owner changed from ascheibe to jkarder
  • Status changed from new to assigned

comment:3 Changed 2 years ago by jkarder

  • Milestone changed from HeuristicLab 3.3.14 to HeuristicLab 3.3.15

comment:4 Changed 18 months ago by gkronber

  • Milestone changed from HeuristicLab 3.3.15 to HeuristicLab 3.3.16

comment:5 Changed 15 months ago by abeham

  • Version 3.3.13 deleted

comment:6 Changed 9 months ago by pfleck

There is an additional issue with the TimeLimitRun and HiveSlaves concerning the Pause/Stop of the underlying algorithm.

When the time limit is reached and the TimeLimitRun is supposed to stop, a Pause event is fired right before the expected Stop event. On a local machine, this is barely noticeable and not a big problem in general. On a Hive slave, however, the first Pause event leads to the Slave pausing the task and resending it to the server, where the server reschedules it for another slave (because the task is paused). Thus, the TimeLimitRun never stops running on Hive.

Note: See TracTickets for help on using tickets.