DistributedCacheNotifier error message when loading data
-
We’re attempting a migration that’s creating a decent number of applications. While under load we see a number for messages in the logs like
ERROR io.fusionauth.api.service.cache.DistributedCacheNotifier - Failed to request a cache reload for [http://10.0.25.29:9011]. Exception message: Connect timed out.
We’ve seen FusionAuth instances get knocked over despite the migration process being single-threaded. If anyone has any suggestions on how to go about this more cleanly it’d be much appreciated.
-
We have had a couple of people have this exception in Kubernetes because the nodes can’t talk to each other. Is your setup configured so that each node can talk to each other node?
I would expect that the configuration would need to use the k8s names rather than IP addresses for all of the nodes. This is configurable in the configuration file or through env variables. More here: https://fusionauth.io/docs/v1/tech/reference/configuration/ . Look for the
fusionauth-app.url
setting.