Repository navigation
Replies: 4 comments
|
Not sure if I understand the new configurations properly, but for distributed caches you may need to set the cache to type to ISPN (as mentioned in the cache configuration page), using |
|
Looking closer at your configuration, I think there is an error. You have the following configuration: This means that you are not using the Also, if you prefer, you could use a |
|
Is cross DC support even ready for Quarkus distributions yet? Below are what I currently observe:
I am a bit confused with the above observations for a cross DC scenario in Keycloak 17. Shall we:
|
|
This discussion might be related : #10694 Anyway, both subject looks important to me and should be addressed soon as this is quite important when deploying with redundancy in mind. another idea would be to propose a way of manually specifying the node in a list instead of relying on the UDP multicast as it seems to have a default TTL of 2 and i can't find where to change that so that it works. |
Uh oh!
There was an error while loading. Please reload this page.
Hello,
At the beginning I will mention that running the configuration within one subnetwork works.
I prepared necessary option in keycloak.conf like a db info and e.g. I didn't change the configuration for cache-ispn.xml
I ran it in order:
bin/kc.sh -Dkc.db-tx-type=enabled -Dkc.db-driver=com.mysql.cj.jdbc.Driver build --db=mysqland after
bin/kc.sh startMy next step was to run keycloak in another DC with different network. I tried to put jgroups configuration at the beginning cache.xml
but it does't work ;/
I have 2 keycloak server per DC.
I tired to do:
Now I am getting such errors:
Can anyone help or send a correct example to do it cross site replication?
Thanks a lot for your help and tips!
All reactions