Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get cluster health from v1/info #264

Merged
merged 1 commit into from
Mar 6, 2024

Conversation

willmostly
Copy link
Contributor

This adds a lightweight health check against the coordinator's v1/info. A cluster is set to healthy as long as the coordinator returns a 200 response and is not in the process of starting. v1/info does not require authentication, which addresses the concerns raised in

@cla-bot cla-bot bot added the cla-signed label Feb 23, 2024
@ebyhr
Copy link
Member

ebyhr commented Feb 24, 2024

Can we deprecate UI API based monitoring?

@mosabua
Copy link
Member

mosabua commented Feb 24, 2024

Can we deprecate UI API based monitoring?

I think ultimately yes .. we still have to chat to the upstream Trino project itself about maybe having a better REST endpoint for cluster health / readiness with info such as attached worker number. I still have to even initiate that discussion

@@ -97,6 +97,22 @@
</exclusions>
</dependency>

<dependency>
<groupId>io.airlift</groupId>
<artifactId>http-client</artifactId>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are we potentially removing OkHttp to use this in the future? Or we will keep both in the repo?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should be able to eliminate the runtime dependency on OkHttp. It is used in several tests, but the gateway itself only uses it in ClusterStatsApiMonitor. We can probably switch over for tests too, just a bit more work.

@willmostly willmostly force-pushed the will/status_only_healthcheck branch 2 times, most recently from a9a0fb5 to 80f3e1c Compare February 29, 2024 19:40
@willmostly willmostly force-pushed the will/status_only_healthcheck branch 3 times, most recently from 6b66c61 to 0bb38f8 Compare March 2, 2024 02:04
@willmostly willmostly force-pushed the will/status_only_healthcheck branch from 0bb38f8 to 0aa7332 Compare March 5, 2024 17:01
@mosabua
Copy link
Member

mosabua commented Mar 5, 2024

Just quick note.. this is definitely the right approach .. we might have it even more useful from the Trino side soon.

Copy link
Member

@Chaho12 Chaho12 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM :)

@willmostly willmostly force-pushed the will/status_only_healthcheck branch from 0aa7332 to 388172f Compare March 6, 2024 17:27
@ebyhr ebyhr merged commit 5337e20 into trinodb:main Mar 6, 2024
2 checks passed
@github-actions github-actions bot added this to the 7 milestone Mar 6, 2024
@ebyhr ebyhr mentioned this pull request Mar 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

None yet

5 participants