You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "paul mackles (JIRA)" <ji...@apache.org> on 2018/04/09 14:33:00 UTC

[jira] [Created] (SPARK-23943) add more specific health check to MesosRestServer

paul mackles created SPARK-23943:
------------------------------------

             Summary: add more specific health check to MesosRestServer
                 Key: SPARK-23943
                 URL: https://issues.apache.org/jira/browse/SPARK-23943
             Project: Spark
          Issue Type: Improvement
          Components: Deploy, Mesos
    Affects Versions: 2.3.0, 2.2.1
         Environment: Added a more robust health-check to MesosRestServer so that anyone who runs MesosClusterDispatcher as a marathon app can use it to check the health of the server:

http://mesosphere.github.io/marathon/docs/health-checks.html

Specifically, this check verifies that the MesosSchedulerDriver is still running as we have seen certain cases where it  dies (rather quietly) and the only way to revive it is a restart. With this health check, marathon will restart the dispatcher if the MesosSchedulerDriver stops running. 

The health check lives at the url "/health" and returns a 204 when the server is healthy and a 503 when it is not (e.g. the MesosSchedulerDriver stopped running).

 
            Reporter: paul mackles
             Fix For: 2.4.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org