redisson: Redisson fails to recognize slave that become a master due to master down in Redis Cluster
Hi Niko, seems like problem really exists with redisson driver for cluster.
Here is our configuration:
aa19c3c2a927384b6a4673539cd7dcdb2efa33e8 10.20.21.113:7001 slave d20242223349a4d51b30da40dad09f0dbc9a2cc8 0 1461081575219 1 connected d20242223349a4d51b30da40dad09f0dbc9a2cc8 10.20.21.44:7000 myself,master - 0 0 1 connected 0-5461 ba12c571516b130a9973fdc95ba8cebbfaf5ac7e 10.20.21.113:7000 master - 0 1461081576222 3 connected 5462-10922 4a21be5ffb25369bf4243918c34467103fa9c8a4 10.20.21.59:7001 slave ba12c571516b130a9973fdc95ba8cebbfaf5ac7e 0 1461081577222 3 connected f6b4e5a94409ca397731165acad90f2193154c62 10.20.21.59:7000 master - 0 1461081576422 0 connected 10923-16383 6a7c1e8510d29aed17dc1e0ca7f0e6a7278b4de5 10.20.21.44:7001 slave f6b4e5a94409ca397731165acad90f2193154c62 0 1461081576721 5 connected
I’m shutting down Redis instances on 10.20.21.113: ba12c571516b130a9973fdc95ba8cebbfaf5ac7e
and aa19c3c2a927384b6a4673539cd7dcdb2efa33e8
When I did this Redis cluster reorganized to following:
aa19c3c2a927384b6a4673539cd7dcdb2efa33e8 10.20.21.113:7001 slave,fail d20242223349a4d51b30da40dad09f0dbc9a2cc8 1461081896304 1461081894700 1 disconnected d20242223349a4d51b30da40dad09f0dbc9a2cc8 10.20.21.44:7000 myself,master - 0 0 1 connected 0-5461 ba12c571516b130a9973fdc95ba8cebbfaf5ac7e 10.20.21.113:7000 master,fail - 1461081896204 1461081895202 3 disconnected 4a21be5ffb25369bf4243918c34467103fa9c8a4 10.20.21.59:7001 master - 0 1461081995791 6 connected 5462-10922 f6b4e5a94409ca397731165acad90f2193154c62 10.20.21.59:7000 master - 0 1461081994787 0 connected 10923-16383 6a7c1e8510d29aed17dc1e0ca7f0e6a7278b4de5 10.20.21.44:7001 slave f6b4e5a94409ca397731165acad90f2193154c62 0 1461081996293 5 connected
As you can see cluster is ok, but requests are failing for some reason. If I restart tomcat without touching anything on Redis requests are not failing. Very strange.
This is the link to the redisson log: https://www.dropbox.com/s/pluyzxtxpd0u23z/redisson.log?dl=0
Please assist, Thank you!
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 23 (13 by maintainers)
Commits related to this issue
- Fixed cluster initialization. #476 — committed to redisson/redisson by deleted user 8 years ago
- Fixed - cluster state update manager can't try next node if current node fails. #476 — committed to redisson/redisson by deleted user 8 years ago
@ybonda At your service!