Repository navigation
Update proxy guide with information about session stickness - #16893
Conversation
There was a problem hiding this comment.
LGTM, thanks.
CC @keycloak/cloud-native @keycloak/store
There was a problem hiding this comment.
So if cluster only has two nodes then both nodes should be holding identical state. This sounds like sticky sessions is more important if you have more than 2 nodes. I assume there is still some time to sync between nodes so session affinity could potentially avoid sync latency
|
@slominskir Yeah, but data availability and their distribution are related to the number of owners you set to our caches (by default, 2 owners) not the number of nodes. It should also be useful if you have only 2 nodes. As you said, you avoid latency if subsequent requests go through the same node during the session lifecycle. Note that this is mainly important for browser-based flows such as authorization code grant type. |
Closes #16892