Quarkus Redis connection issues #40527
Unanswered
krezchikov42
asked this question in
Q&A
Replies: 2 comments
-
/cc @Ladicek (redis), @cescoffier (redis), @machi1990 (redis) |
Beta Was this translation helpful? Give feedback.
0 replies
-
There is a straightforward reconnect on error functionality in the Vert.x Redis client (contrary to the documentation, perhaps that should be updated) in the form of connection pooling. When a connection enters an error state, it is removed from the pool and a new one is created. Could you use a newer Quarkus version? It includes a newer Vert.x Redis client, which includes more descriptive error messages. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
So I have been seeing these errors lately.
"io.vertx.core.impl.NoStackTraceThrowable: Failed to connect to all nodes of the cluster"
I have seen these mentioned in issues like this #37348 and #37041
However, I'm not sure if using the
ReactiveRedisDataSource
I am allowing for the connection to reconnect on error. I know in Vert.x you have to manually implement the reconnect on errror. How would I do this when I am using theReactiveRedisDataSource
?I don't see any information about reconnecting on error in the quarkus redis documentation
Beta Was this translation helpful? Give feedback.
All reactions