You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Lettuce doesn't seems able to recognize topology changes if the first configured sentinel node goes down with the master.
Even configuring a periodic topology refresh seems to be uneffective.
I know from this discussion that looking for master by just one sentinel is a desired behavior, it exists any workaround or procedure to re-establish connection to the correct master?
Update: It seems that the affected connection are the one already established by the pool, new connections works like a charm.
The issue related to the pending pool connection seems to be related to L3 tcp timeout problem discussed in this issue,
I'll update and eventually close the issue after some other tests.
Lettuce doesn't seems able to recognize topology changes if the first configured sentinel node goes down with the master.
Even configuring a periodic topology refresh seems to be uneffective.
I know from this discussion that looking for master by just one sentinel is a desired behavior, it exists any workaround or procedure to re-establish connection to the correct master?
Update: It seems that the affected connection are the one already established by the pool, new connections works like a charm.
Redis configuration:
Scenario:
Spring boot application is connected to Redis by sentinels through lettuce with pool.
Spring boot configuration:
Stacktrace:
Thanks,
Angelo
The text was updated successfully, but these errors were encountered: