Repeated "Node is no longer available in the topology" when the node is up and running #1091
-
Can anyone explain why this is happening? Is it a sign of something being mis-configured? Can we safely ignore it? Trace level logs from a login request. :
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hi @efenderbosch-atg, yes you can safely ignore this log message. When the client application makes the initial connection using a cluster endpoint, the driver will add the provided endpoint to the topology cache in memory. When the failover plugin fetches the actual topology, the cluster endpoint will be replaced by the instance endpoints, hence the logs you are seeing. These log messages are pretty low level, if you'd like you can increase the log level to see less of these debug messages.
More details on logging here. |
Beta Was this translation helpful? Give feedback.
Hi @efenderbosch-atg, yes you can safely ignore this log message.
When the client application makes the initial connection using a cluster endpoint, the driver will add the provided endpoint to the topology cache in memory. When the failover plugin fetches the actual topology, the cluster endpoint will be replaced by the instance endpoints, hence the logs you are seeing.
These log messages are pretty low level, if you'd like you can increase the log level to see less of these debug messages.
You can use a
.properties
file to modify the log level: