TimeLimitRun does not work with the Hive Slave

[ascheibe]

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

[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.

[gkronber]

This problem has become more severe.

Currently, the TimeLimitRun crashes the hive worker.

[abeham]

I will take a look into it. I will try to change that the Pause events of the underlying Algorithm do not cause a Pause in the TimeLimitRun when only a snapshot is to happen. Then, hopefully the worker will not be aware of the Pause event.

[abeham]

r16651: Decoupled execution state of timelimitrun and its embedded algorithm

The TimeLimitRun should now not Pause anymore when it is creating a Snapshot. Please try if this works for you.

[gkronber]

I tested the changes locally and on hive using an experiment with batch runs of TimeLimitRun with GA - TSP. It seems to work now.

Reviewed r16651.

[gkronber]

Must be merged with/after persistence.

[abeham]

r17115: merged to stable (16651)