-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
HIVE-28775: HiveServer2: introduce a new HA Health Check endpoint on a different p… #5652
base: master
Are you sure you want to change the base?
Conversation
how about skipping the authentication for |
If we do that and Hive is deployed on a public cloud, it will allow access to the /leader endpoints to the internet, which is not secure. By adding a new unsecured endpoint for HA health-check on a different port, that new port can be exposed internally only for health-check script which will be more secure. |
f65e8fe
to
4917037
Compare
|
…ort than WebUI
What changes were proposed in this pull request?
Changes to deploy a new endpoint for HA health checking that listens on a different port than WebUI port on HS2 webserver.
Why are the changes needed?
Leader endpoint is used for HA health checking on downstream. When LDAP authentication is enabled on HS2, it requires to call leader endpoint with LDAP also. If we wanted to create a technical user for this endpoint we would need to have customers add this user into their LDAP servers which we have no control over, so this is not a good solution. Instead of that this PR proposes a new HA health check endpoint that exposes only the new route '\GET /health-ha/leader' on a different port that can be accessed without LDAP.
Does this PR introduce any user-facing change?
Yes, new http endpoint that listens on a different port.
Is the change a dependency upgrade?
No.
How was this patch tested?
Execution of existing precommit tests + new HA tests.