YARN-7052. RM SchedulingMonitor gives no indication why the spawned thread crashed. Contributed by Eric Payne
(cherry picked from commit 39a9dc8e4a
)
This commit is contained in:
parent
b0e951725f
commit
dfdda969ad
|
@ -102,9 +102,11 @@ public class SchedulingMonitor extends AbstractService {
|
|||
try {
|
||||
//invoke the preemption policy
|
||||
invokePolicy();
|
||||
} catch (YarnRuntimeException e) {
|
||||
LOG.error("YarnRuntimeException raised while executing preemption"
|
||||
+ " checker, skip this run..., exception=", e);
|
||||
} catch (Throwable t) {
|
||||
// The preemption monitor does not alter structures nor do structures
|
||||
// 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