Skip to content
This repository has been archived by the owner on Mar 8, 2022. It is now read-only.

Keycloak doesn't re-evaluate DNS for the database #63

Closed
cvarjao opened this issue Dec 19, 2019 · 3 comments
Closed

Keycloak doesn't re-evaluate DNS for the database #63

cvarjao opened this issue Dec 19, 2019 · 3 comments

Comments

@cvarjao
Copy link
Member

cvarjao commented Dec 19, 2019

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.

@brycereid73
Copy link
Contributor

Test if this is still an issue in Sandbox.

@arcshiftsolutions
Copy link
Contributor

This is still an issue; our team had issues during a node drain recently.

@zsamji
Copy link

zsamji commented Jan 5, 2022

closing and tracking here bcgov/sso-keycloak#72

@zsamji zsamji closed this as completed Jan 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants