-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Simple HTTP based healthcheck implementation for cloud environments that support rolling restarts like Openshift or Google Cloud Engine #9284
Conversation
run-lab-run |
Test PASSed. |
Looks good. Can you add some tests? |
How can I test that? I mean it's disabled in mocks, so I would have to create a real cluster node which is bad for parallel testing. Any idea? |
You can also make it a nightly test and have it run in isolation. |
Test PASSed. |
Can we get this merged? :) |
👍 |
run-lab-run |
Test PASSed. |
Thanks @noctarius ! Can we update documentation with that API addition? cc: @Serdaro |
This PR adds a very basic health check to the Hazelcast HTTP subsystem that provides information about the current health status (ongoing migrations, cluster size, ...). That way monitoring solutions or ready / health checks can be implemented on the cloud environment side.
The information provided are minimal to not interfere too much with the cluster load. Requests to
http://xxx.xxx.xxx.xxx:5701/hazelcast/health
are accepted whenever the propertyhazelcast.http.healthcheck.enabled
is set to true. In this case a GET request provides a result like the following:Based on this result the check can make assumptions like "the cluster is not yet safe, I cannot go on with rolling restarts".