Running our processes today we received the following: "Microsoft.Hpc.Scheduler.Session.SessionException: Failed to get job owner from the scheduler." from a couple of the jobs we submitted (within 2 seconds of each other) and was hoping to better
understand what was going on and hopefully fix the underlying issue if we can. Re-running the process it worked fine so seems some sort of transient issue.
I googled the error and found 1 reference to an older forum post but can't seem to get any information on what this error might actually mean. We do not use the cached credentials option, and pass a user/pass each run. As mentioned in the other
post, we are currently initializing multiple DurableSession/ClientBrokers, so wondering if it could be another manifestation of too much load on either the client or head machine. We currently do not have any dedicated broker nodes, but can add those
if you think might be helpful.
Thanks!
-Jason
