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 am trying to set up clustering for Keycloak 18. I have tried both JDBC_PING(stack=tcp) and DNS_PING(stack=kubernetes) and can see cluster formation and node discoveries in the log for two of AWS cluster.
However when I am trying to run the same code on AWS EC2 instance clustering is not working correctly.
1)For JDBC_PING ,the issue is table is getting created and storing only one node information and node are not able to discover each other
2)For DNS_PING ,nodes are not able to discover each other even after using same headless service which I used for other AWS instances.
Below is the complete setup I am using for the two
For JDBC_PING
Setting env value as
ENV KC_CACHE_CONFIG_FILE=cache-jdbc-ping-ispn.xml
where cache-jdbc-ping-ispn.xml contains below stack information
Adding env variable as JAVA_OPTS_APPEND="-Djgroups.dns.query=keycloak-headless"
Let me know if I am missing something here and any suggestion over why the issue is present on ec2 instance
Also I have been trying using cache-stack=ec2 where facing lots of issues.
If someone provides some reference or guidance about setting up the clustering using ec2(what jar needs to be added, region and bucket information, etc) then it will be very helpful .
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I am trying to set up clustering for Keycloak 18. I have tried both JDBC_PING(stack=tcp) and DNS_PING(stack=kubernetes) and can see cluster formation and node discoveries in the log for two of AWS cluster.
However when I am trying to run the same code on AWS EC2 instance clustering is not working correctly.
1)For JDBC_PING ,the issue is table is getting created and storing only one node information and node are not able to discover each other
2)For DNS_PING ,nodes are not able to discover each other even after using same headless service which I used for other AWS instances.
Below is the complete setup I am using for the two
For JDBC_PING
Setting env value as
ENV KC_CACHE_CONFIG_FILE=cache-jdbc-ping-ispn.xml
where cache-jdbc-ping-ispn.xml contains below stack information
For DNS_PING
Usnig env variables as
ENV KC_CACHE=ispn
ENV KC_CACHE_STACK=kubernetes
and creating headless service as
apiVersion: v1
kind: Service
metadata:
name: keycloak18-headless
spec:
clusterIP: None
selector:
app: dssecuritykeycloak17
ports:
- name: http
port: 8080
protocol: TCP
targetPort: http
- name: jgroups
port: 7600
protocol: TCP
targetPort: jgroups
sessionAffinity: None
type: ClusterIP
Adding env variable as JAVA_OPTS_APPEND="-Djgroups.dns.query=keycloak-headless"
Let me know if I am missing something here and any suggestion over why the issue is present on ec2 instance
Also I have been trying using cache-stack=ec2 where facing lots of issues.
If someone provides some reference or guidance about setting up the clustering using ec2(what jar needs to be added, region and bucket information, etc) then it will be very helpful .
All reactions