[
https://issues.apache.org/jira/browse/DRILL-6406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hari Sekhon updated DRILL-6406:
-------------------------------
Summary: Apache Drill /status unreliable - add Proper Health Check to API -
/status returns "Running" even though Drill isn't usable eg. java classpath
errors for flexjson-*.jar when trying to execute any query (was: Apache Drill
Add Proper Health Check to API - /status returns "Running" even though Drill
isn't usable eg. java classpath errors for flexjson-*.jar when trying to
execute any query)
> Apache Drill /status unreliable - add Proper Health Check to API - /status
> returns "Running" even though Drill isn't usable eg. java classpath errors
> for flexjson-*.jar when trying to execute any query
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DRILL-6406
> URL: https://issues.apache.org/jira/browse/DRILL-6406
> Project: Apache Drill
> Issue Type: Bug
> Components: Server, Client - HTTP, Execution - Monitoring, Tools,
> Build & Test, Web Server
> Affects Versions: 1.10.0, 1.13.0
> Reporter: Hari Sekhon
> Priority: Major
>
> I've come across situations on MapR 5.2 / 6.0 where Drill 1.10 / 1.13 is up
> and running but there are flexjson jar classpath errors meaning that Drill is
> not usable so queries fail even though the API gives the impression that
> Drill is available. This is bad for load balancers.
> This API needs to be much more robust and terms of checking if Drill is fully
> working. I suggest internally doing a health check real query and if that
> executes successfully and returns the expected result, only then updating the
> status to OK / Running.
> This internal health check query should be periodically re-executed (eg.
> every 30 secs) and the status set to ERROR or something if if fails.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
