Keycloak doesn't re-evaluate DNS for the database #72
zsamji
announced in
Operations
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
When patroni failover to a new master, keycloak doesn't seem to detect that and keeps re-using the IP of the previous master which is now in read-only mode. It seems to keep a lock to the IP.
It may be related to java DNS lookup caching
Workaround: Flush connections to fore connections to be established.
Sept 2021: This is still an issue; our team had issues during a node drain recently.
Reference: bcgov/ocp-sso#63
Beta Was this translation helpful? Give feedback.
All reactions