airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Semet (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-1084) `/health` endpoint on each component
Date Fri, 09 Mar 2018 16:56:00 GMT

    [ https://issues.apache.org/jira/browse/AIRFLOW-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16393162#comment-16393162
] 

Semet commented on AIRFLOW-1084:
--------------------------------

ideally for web, a "ready" end point could also be implemented to drive the ingress on/off
in case of overload. Not really mandatory, but fun to have :)

> `/health` endpoint on each component
> ------------------------------------
>
>                 Key: AIRFLOW-1084
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-1084
>             Project: Apache Airflow
>          Issue Type: Improvement
>            Reporter: Semet
>            Priority: Major
>
> Please provide a {{/health}} endpoint of each of the following component: 
> - webservice (to avoid pinging the {{/}} root endpoint)
> - worker
> - scheduler
> This would ease integration in Mesos/Marathon framework. 
> If you agree, I volunteer to add this change.



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

Mime
View raw message