Closed tanema closed 7 years ago
still trying to figure this out, when I try and set it all up in the console by doing r = Redis.new(options) r.sentinel('sentinels', 'master') fails but r.client.current_sentinel.sentinel('sentinels', 'master') works
when I inspect them r has a wrong port of 6379 when all my sentinels have the port 26379
okay so it turns out it may be a jruby problem. I switched to jruby 1.7.10 (which the project is using) and ran your tests and got the exact same error
moved up to just jruby-1.7.11 and it works. that was not fun.
@tanema I didn't try redis-sentinel in jruby, but I guess it's caused by _parse_sentinel_options
, could you try the latest master?
I keep getting this error no matter what the config here is the stacktrace: Stacktrace:
Here is what my config looks like:
It of course only happens in production, and I tried doing it all in the console and I get the same errors, however I can get all_clients and for some odd reason it works if I Redis.new().client.current_sentinel.
Any help explaining this would be really appreciated