keycloak + infinispan getting error - Event object wasn't available in remote cache after event was received. Event key: 09de68ed-b042-4306-97f9-0f420c67e9cb

My cluster has been getting this error and tried googling and this is the closest issue i found. https://github.com/keycloak/keycloak/issues/25322

My setup, keycloak with infinispan backed by postges setup.  After reviewing my cluster setup, I notice that my statefulset created some ghost pod - meaning keycloak CRD states that it is 3 replicas, while my kubernetes statefulset is 6. And yes, some one update the STS manually and causes this issue.

Why is solving this issue is important? Keycloak node will get into a crazy GC collection stage retrying alot of the operation again and again. And your keycloak node becomes really busy and before you know it, your keycloak pod is flagged as 'unhealty'

My fix: I ensure the STS and keycloak replicas are in sync with each other - same replica. 

kubectl edit sts/keycloak -n keycloak-wwnz

And then ensure replica is 5. 






 







Comments

Popular posts from this blog

vllm : Failed to infer device type

gemini cli getting file not defined error

NodeJS: Error: spawn EINVAL in window for node version 20.20 and 18.20