KNOX-843 - Client side HA #380
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This PR introduces a way for Knox to load balance backend clients. This is done by introducing 3 parameters in
HaProviderenableStickySession- Enables sticky sessionsstickySessionCookieName- Customize sticky session cookie name, default is KNOX_BACKEND-{serviceName}noFallback- when this flag is set, Knox will return a 502 (Bad Gateway) if a request comes with a cookie and the corresponding backend is unavailable. This is applicable only whenstickySessionCookieNameis enabled.enableLoadBalancing- Enable loadbalancing, roundrobin requests to backend HA urlsWhen enabled, knox dispatch will round-robin requests to the URLs listed in the HA configuration unlike previously where knox only chooses other URL after a failover.
The sessions are sticky so same session requests will always end up dispatching to the same backend.
How was this patch tested?
This patch was manually tested using