INFO_API doesn't expose queuedQueryCount and runningQueryCount
andythsu opened this issue · comments
By design, queuedQueryCount and runningQueryCount are updated from health checks. However, /v1/info doesn't expose queuedQueryCount and runningQueryCount, which are the two important values for QueryCountBasedRouter to work properly. When using QueryCountBasedRouter, it is best to use other health check mechanism such as UI_API or JDBC
We should merge UI_API and INFO_API together
This would be a good enhancement, may be we should have a single status endpoint which trino can expose the user and cluster stats without the authentication.
Oh so this why queued/running count is always 0 (info api) -> we should explain this in doc
