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
Looking at redis/lettuce#339 (comment) it appears that there is a strong case to enable a periodic refresh even when using adaptive-refreshes. For example, a failed replica does not trigger a refresh -- clients first receive a trigger (such as a MOVED result) to trigger that kind of refresh, which won't necessarily happen.
Existing behavior could be achieved by making the 'default' interval exceptionally long and allowing the client to select a lower value.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Looking at redis/lettuce#339 (comment) it appears that there is a strong case to enable a periodic refresh even when using adaptive-refreshes. For example, a failed replica does not trigger a refresh -- clients first receive a trigger (such as a MOVED result) to trigger that kind of refresh, which won't necessarily happen.
Existing behavior could be achieved by making the 'default' interval exceptionally long and allowing the client to select a lower value.
The text was updated successfully, but these errors were encountered: