Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Next »

If at anytime it is observed that Keycloak is not reachable and not up and running we need to perform below mentioned steps:
1. Restart the keycloak pods and wait for it to come back.
2. Restart the Datashare service pod once keycloak is restarted.

Description: We generally face this issue if overall no of sessions there exceeds ~70K.
We should not end up in this situation if the keycloak sessions is being monitored on timely basis and sessions are getting cleared using the script provided.
Below is the link for the instructions to logout the sessions of a client in keycloak realm.

  • No labels