horizon: Configure stickiness with haproxy #841
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We use cookie-based stickiness for non-SSL, and we also expire the stickiness based on the session timeout. This should make the haproxy/horizon combo to work well, with each session sticking to one backend, thus avoiding potential issues where requests are spread between multiple backends. Note that we use two cookies: - sessionid, which identifies a session - csrftoken, which identifies a "login session", before a real session really exists, with the proper sessionid token
This was referenced Feb 8, 2017
Since horizon is really used by browsers, the affinity based on SSL session ID is not enough because the browsers open multiple connections. To make sure a user always ends up on the same backend, we enforce the balance strategy to be "source" (that is based, on the the client IP address).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We use cookie-based stickiness for non-SSL, and we also expire the
stickiness based on the session timeout. This should make the
haproxy/horizon combo to work well, with each session sticking to one
backend, thus avoiding potential issues where requests are spread
between multiple backends.
Depends on crowbar/crowbar-ha#179