Skip to content

Repeated "Node is no longer available in the topology" when the node is up and running #1091

Answered by karenc-bq
efenderbosch-atg asked this question in Q&A
Discussion options

You must be logged in to vote

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:

.level=INFO
handlers=java.util.logging.ConsoleHandler
java.util.logging.ConsoleHandler.level=ALL
software.amazon.jdbc.Driver.level=FINEST
softwa…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by efenderbosch-atg
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants