cannot connect to redis sentinel using Lettuce if one of the sentinels is down #304

Closed
RamirezTuco opened this Issue Jul 6, 2016 · 1 comment

Projects

None yet

2 participants

@RamirezTuco
RamirezTuco commented Jul 6, 2016 edited

Make sure that:

  • You have read the contribution guidelines.

  • You specify the lettuce version and environment so it's obvious which version is affected

  • You provide a reproducible test case (either descriptive of as JUnit test) if it's a bug or the expected behavior differs from the actual behavior.

We are unable to connect to redis-sentinel using Lettuce if we provide three sentinels and one of them is down.
If one of the machine goes down, then lettuce is unable to connect to sentinel.
However, if the server is up and running, then it works well, and it seems to give timeouts for new connections.

@mp911de mp911de added a commit that referenced this issue Jul 7, 2016
@mp911de Allow MasterSlave connection using Sentinel if some Sentinels are not…
… available #304

MasterSlave can now still establish a connection even if one or more Sentinel servers are down. This works as long as at least one Sentinel server is available.
966292c
@mp911de mp911de added a commit that referenced this issue Jul 7, 2016
@mp911de Allow MasterSlave connection using Sentinel if some Sentinels are not…
… available #304

MasterSlave can now still establish a connection even if one or more Sentinel servers are down. This works as long as at least one Sentinel server is available.
9ce7259
@mp911de mp911de added the bug label Jul 7, 2016
@mp911de mp911de added this to the Lettuce 4.3.0 milestone Jul 7, 2016
@mp911de
Owner
mp911de commented Jul 7, 2016

Fixed by allowing one or more unavailable Sentinels.

@mp911de mp911de closed this Jul 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment