I did not see an exception/error in the logs. I'd imagine if one was caught
by the JNI binding, then I 'd see the message in stderr. I don't have those
logs now, though.
You are right, Mantis is a JVM framework.
Mantis was up and responding to everything else, except it had no offers to
assign res
My guess is that your driver threw an exception while handling the
offerRescinded() callback which was detected by the JNI binding (IIRC
Mantis is a JVM framework?) causing it to abort the driver. Note that when
a driver aborts, it will send a DeactivateFrameworkMessage to the master
causing the ma
We had this problem show up yesterday, just one time, that I don't
understand. Would appreciate any help.
This is the sequence of events, as far as I can tell:
>From framework's perspective:
F1: framework got an offer from a host that it decided it will not use, so
it declines it
F2: got schedule
3 matches
Mail list logo
