YARN-7052. RM SchedulingMonitor gives no indication why the spawned thread crashed. Contributed by Eric Payne
This commit is contained in:
parent
8455d70756
commit
39a9dc8e4a
|
@ -100,9 +100,11 @@ public class SchedulingMonitor extends AbstractService {
|
||||||
try {
|
try {
|
||||||
//invoke the preemption policy
|
//invoke the preemption policy
|
||||||
invokePolicy();
|
invokePolicy();
|
||||||
} catch (YarnRuntimeException e) {
|
} catch (Throwable t) {
|
||||||
LOG.error("YarnRuntimeException raised while executing preemption"
|
// The preemption monitor does not alter structures nor do structures
|
||||||
+ " checker, skip this run..., exception=", e);
|
// persist across invocations. Therefore, log, skip, and retry.
|
||||||
|
LOG.error("Exception raised while executing preemption"
|
||||||
|
+ " checker, skip this run..., exception=", t);
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in New Issue