-
Notifications
You must be signed in to change notification settings - Fork 987
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
Cannot refresh Redis Cluster topology #1706
Comments
I'm seeing almost exactly the same issue. Lettuce version: 6.1.0.RELEASE Stack trace
Code public RedisClusterClient createClusteredClient(RedisConfig redisConfig) {
RedisClusterClient client = RedisClusterClient.create(clientResources, redisConfig.redisURI());
ClusterTopologyRefreshOptions topologyRefreshOptions = ClusterTopologyRefreshOptions.builder()
.enablePeriodicRefresh(Duration.of(10, ChronoUnit.MINUTES))
.enableAllAdaptiveRefreshTriggers()
.build();
client.setOptions(ClusterClientOptions.builder()
.topologyRefreshOptions(topologyRefreshOptions)
.autoReconnect(redisConfig.isAutoReconnect())
.pingBeforeActivateConnection(redisConfig.isPingBeforeActivateConnection())
.cancelCommandsOnReconnectFailure(redisConfig.isCancelCommandsOnReconnetFailure())
.socketOptions(SocketOptions.builder()
.keepAlive(redisConfig.isSoKeepAlive())
.connectTimeout(Duration.of(redisConfig.getSoConnectTimeoutMillis(), ChronoUnit.MILLIS))
.build())
.build());
return client;
} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Current Behavior
I've found that the WARN log message is "Cannot refresh Redis Cluster topology", after AWS Elasticache instance reboot.
Although the log was printed every topology refresh period, all requests was fine.
Stack trace
Input Code
Input Code
Expected behavior/code
"Cannot refresh Redis Cluster topology" log should no longer be printed.
Environment
The text was updated successfully, but these errors were encountered: