Closed jhpoelen closed 6 years ago
Seems to have lost consistency:
HTTP ERROR: 503
Problem accessing /. Reason:
Could not determine the current leader
Powered by Jetty:// 9.3.z-SNAPSHOT
Restart on all nodes has brought it back up. Two possible causes: the last logs were requests from the UFIT security scanner (a classic destroyer of services) and Tuesday I filled up HDFS for about an hour though Marathon proper doesn't use HDFS for anything, only it's services do.
Thanks for responding. Looks like marathon and the api are back up, see attached. . Curious to learn more about the root causes.
Marathon, the service that runs the api and spark job dispatcher, is no longer running for reasons unknown.