In order to better understand root causes of issues such as e.g. GENIUS-58 in the future, it would be useful if the JobCoordinator (ex-DataStoreJobCoordinator; about to be moved from genius to infrautils in https://git.opendaylight.org/gerrit/#/c/51431/) for job failures should indicate stack trace of original caller who submitted job.

NB: https://bugs.opendaylight.org/show_bug.cgi?id=7917#c3

"Adding appropriate info in the caller's mainWorker toString would help to identify the originator. However I think capturing the caller's stack trace would be too expensive in production although it could be done in a debug mode."

I'm wondering how other Java frameworks deal with not loosing the stack of the original caller when working with async lambdas in Java .. there must be some.. "prior art" in this domain? Perhaps worth trying to learn a bit more about this through online research, before jumping into an implementation.