Problem with redis-sentinel + resque about redis-sentinel HOT 7 CLOSED

I'm not completely sure what "too large fdsets" really means, but it seems to deal with file descriptors. The commit that was merged in a bit ago for pull request #3 fixed a leaky file descriptor. Try using the master branch and see if that fixes the problem.

from redis-sentinel.

@JohnBat26 why the error indicates you are using hiredis but I didn't see it from you code?

from redis-sentinel.

@flyerhzm this is part of my Gemfile:

  gem 'resque', '1.23.0', :require => 'resque/server'
  gem 'resque-scheduler', '2.0.0'
  gem 'resque-retry'
  gem 'redis-namespace', '1.2.1'
  gem 'resque-workers-lock'
  gem 'redis-sentinel'
  gem 'hiredis', '0.4.5'
  gem 'redis', '~>3.0.2', :require => %W(redis/connection/hiredis redis)
  gem 'redis-rails'

this is my resque_auth.rb (from config/initializers):

require 'yaml'
require 'resque'
require 'resque_scheduler'
require 'resque/scheduler'
require 'resque_scheduler/server'

Resque::Scheduler.dynamic = true
 Resque.redis = Redis.new(master_name: "webcol-med01", sentinels: [{host: "webcol-med01", port: 26379}, {host: "webcol-med02", port: 26379}])
#   Resque.redis = 'webcol-med01:6379' # tell Resque where redis lives

from redis-sentinel.

@JohnBat26, I have reproduced your issue only when redis sentinel servers are not up, can you make sure your redis sentinel servers works?

redis-cli -h webcol-med01 -p 26379
redis-cli -h webcol-med02 -p 26379

from redis-sentinel.

redis-cli -h webcol-med01 -p 26379
redis webcol-med01:26379>
redis-cli -h webcol-med02 -p 26379
redis webcol-med02:26379>

I have installed git version of redis-sentinel gem but now after start resque, redis-sentinel proccess use 50 СPU! and resque hungs without logs :(

from redis-sentinel.

It's hard for me to reproduce. How many CPU usage before using redis-sentinel?

If resque hung, there must be something wrong with the connection, could you confirm if your ruby process connects to redis sentinel server and also it connects to redis master server?

from redis-sentinel.

Sorry, it is my mistake.
I inserted wrong master_name. :)
Now, all works correctly.

from redis-sentinel.