You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried using JDBC_PING protocol for keycloak clusterization. The setup works fine on local, but we have problems establishing the same on Azure
I am deploying 2 keycloak instances as Azure web apps using shared Azure flexible postgresql DB, latest quay image and provided cache-ispn-jdbc-ping.xml.
In jgroups ping table I am seeing
I can see that when the app service instances start, I only end up with a single record in the JGROUPSPING table. I can see that each node adds a record with the nodes IP address (private dns zone record in my case) which is then replaced by the next node that starts up.
That would mean that my 2 keycloak instances work as singleton (which I see in the logs) and actually are not clusterized.
Is this some limitation on communication between Azure App Services on port 7600 or something else?
The text was updated successfully, but these errors were encountered:
I tried using JDBC_PING protocol for keycloak clusterization. The setup works fine on local, but we have problems establishing the same on Azure
I am deploying 2 keycloak instances as Azure web apps using shared Azure flexible postgresql DB, latest quay image and provided cache-ispn-jdbc-ping.xml.
In jgroups ping table I am seeing
I can see that when the app service instances start, I only end up with a single record in the JGROUPSPING table. I can see that each node adds a record with the nodes IP address (private dns zone record in my case) which is then replaced by the next node that starts up.
That would mean that my 2 keycloak instances work as singleton (which I see in the logs) and actually are not clusterized.
Is this some limitation on communication between Azure App Services on port 7600 or something else?
The text was updated successfully, but these errors were encountered: