Evaluator idle gets killed

[Tyson Condie <tc...@gmail.com>]

Is it the case that an idle Evaluator gets killed? I ask because my (idle)
Evaluator gets killed, and when I drill down to the evaluator.stderr I see
the following (specifically the last line):
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m;
support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
MaxPermSize=128m; support was removed in 8.0
Aug 24, 2017 3:21:17 PM org.apache.reef.runtime.common.REEFLauncher main
INFO: Entering REEFLauncher.main().
Aug 24, 2017 3:21:18 PM org.apache.reef.util.REEFVersion logVersion
INFO: REEF Version: 0.16.0
Aug 24, 2017 3:21:18 PM
org.apache.reef.runtime.common.evaluator.context.defaults.DefaultContextStartHandler
onNext
INFO: DefaultContextStartHandler received:
org.apache.reef.runtime.common.evaluator.context.ContextStartImpl@708f5957
Aug 24, 2017 3:21:18 PM
org.apache.reef.wake.impl.MissingStartHandlerHandler onNext
WARNING: No binding to Clock.StartHandler. It is likely that the clock will
immediately go idle and close.

If (for some reason) idle evaluators are not allowed, then how do I
configure an Evaluator to not be idle... basically, I want to hold on to
Evaluators, running tasks every now and then.

Thanks,
Tyson Condie

Re: Evaluator idle gets killed

[Markus Weimer <ma...@weimo.de>]

Welcome back to the list, Tyson!

On Thu, Aug 24, 2017 at 3:46 PM, Tyson Condie <tc...@gmail.com> wrote:
> Is it the case that an idle Evaluator gets killed? I ask because my (idle)
> Evaluator gets killed, and when I drill down to the evaluator.stderr I see
> the following (specifically the last line):

No. Evaluators have a life time controlled by the application. There
is not automatism in REEF that shuts down idle Evaluators.

> org.apache.reef.wake.impl.MissingStartHandlerHandler onNext
> WARNING: No binding to Clock.StartHandler. It is likely that the clock will
> immediately go idle and close.

I believe this is just a very unfortunate log message. In the Driver,
this message is correct. In the Evaluator, it doesn't make much sense.
Unfortunately, we use the exact same default implementation for
`EventHandler<StartTime>` in both. If the `Clock` goes idle, it
triggers an event of type `IdleClock`. In the Driver, we have an event
handler for that which shuts the Driver down. In the Evaluator, that
is not the case. Just to be very sure: Do you see other mentions of
`Idle` or `IdleClock` in your log files?

Assuming that you don't, the reason for the shutdown must be elsewhere
:(. Do you get a `FailedEvaluator` event in the Driver?

Markus