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
It depend on health of redis clusters. When one master node goes down, redis clusters will be in self recovery. It maybe some error to execute command. After recovery completed, it will be fine to execute command.
@zhchsf,
The new master is elected in less than a second. How can reconnection be tried in this case to connect to the newly elected master instead of breaking code?
I have above code snippet running, but when 10.0.0.1:7000 master in cluster goes down, it simply break, does not insert data in new master
/usr/local/rvm/gems/ruby-2.5.1/gems/redis-3.3.5/lib/redis/client.rb:121:in
call': MOVED 3300 10.0.0.1:7000 (Redis::CommandError)`redis_cluster (0.3.2)
redis version: 4.0.11
The text was updated successfully, but these errors were encountered: