New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lettuce suppresses initial exception in Redis Cluster #427
Comments
The only way to get a cause is by initially throwing an exception from The main question is: When to throw an exception?
What do you think? The exception needs to be handled in the background refresh job ( |
In my case I want to show human readable message about problem if my application couldn't establish initial connection to Redis Cluster at all (after call of So, as you can see I don't want to change current behavior of lettuce. I just want to see initial exception from all seed nodes or from last seed node only if the lettuce couldn't establish initial connection to Redis Cluster. |
…427 RedisClusterClient.loadPartitions now propagates the cause if lettuce can't connect to any of the topology refresh sources (initial seed nodes). Cause propagation covers I/O errors and authentication issues. Command execution issues are just logged.
…427 RedisClusterClient.loadPartitions now propagates the cause if lettuce can't connect to any of the topology refresh sources (initial seed nodes). Cause propagation covers I/O errors and authentication issues. Command execution issues are just logged.
That's implemented now. A possible stack trace can look like:
|
Excellent! :) I see all suppressed exceptions too. Thank you! |
spring.redis.timeout: 1000 |
Not exactly sure what you're trying to express @hackpros. Care to elaborate, possibly in a new ticket? |
For example I set invalid password and want to connect to Redis Cluster. In this case Lettuce suppress initial exception:
and raise new exception here without any information about initial exception.
How do you think is it possible to pass initial exception in
getCause()
method of new exception?Lettuce 4.3.0.Final
The text was updated successfully, but these errors were encountered: