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.
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.
Fixed by allowing one or more unavailable Sentinels.
Eager initialization of API wrappers in stateful connections #304