This message was deleted.
# troubleshooting
s
This message was deleted.
h
Hey, this looks like a JobMaster Global failure. It might have caused the JobManager to restart entirely. If you’re using a container, the log scraping mechanism might have missed out on these logs - probably worth checking if any logs have been dropped
What container orchestration system are you using? For .e.g for kubernetes you can get the previous container logs using
kubectl logs <pod> -p
Right… sorry am not too familiar with YARN container orchestration..