Config global state for standalone Keycloak 22.0.5 #26095
Unanswered
phoenix-ua
asked this question in
Q&A
Replies: 2 comments
-
Can you close this discussion in favor of #29384 ? That one has more troubleshooting data. |
Beta Was this translation helpful? Give feedback.
0 replies
-
The warning can be safely ignored because Keycloak does not use any Infinispan feature that requires the global state. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Greetings,
Our team uses a single standalone on-premise Keycloak 8.0.1 instance and we're migrating it to Keycloak 22.0.5. We noticed a couple of warning messages during Keycloak boot and the one I'm worried about is:
Is this warning an indicator of any problem that has to be fixed in my specific case with a single Keycloak instance? I never faced a 'global state' notion in Keycloak before.
I consulted with Configuring Keycloak for production and Configuring distributed caches docs but only found recommendations for multi-node Keycloak clusters and nothing about standalone installations. Maybe there are examples of standalone Keycloak configuration without such warning messages or I missed something?
I will be grateful for any assistance or hints
Beta Was this translation helpful? Give feedback.
All reactions