when I restart the redis master the jobs stop

[juanpabloaj]

Description

I have a bull code example and a redis with replication when I restart the redis master the jobs stop and I get this message

...
processing video 59969
processing video 59970
processing video 59971
processing video 59972
processing video repeat:6f7759385e855ae9ce8f89c1765be3a3:1563459010000
processing video 59976
processing video repeat:6f7759385e855ae9ce8f89c1765be3a3:1563459011000
processing video 59978
Error in bull queue happend: Error: read ECONNRESET
Error in bull queue happend: Error: read ECONNRESET
Error in bull queue happend: Error: read ECONNRESET
Error in bull queue happend: Error: read ECONNRESET
Error in bull queue happend: Error: connect ECONNREFUSED 127.0.0.1:6379
Error in bull queue happend: Error: connect ECONNREFUSED 127.0.0.1:6379
Error in bull queue happend: Error: connect ECONNREFUSED 127.0.0.1:6379
Error in bull queue happend: Error: connect ECONNREFUSED 127.0.0.1:6379
Error in bull queue happend: Error: connect ECONNREFUSED 127.0.0.1:6379
Error in bull queue happend: Error: connect ECONNREFUSED 127.0.0.1:6379
Error in bull queue happend: Error: connect ECONNREFUSED 127.0.0.1:6379
Error in bull queue happend: Error: connect ECONNREFUSED 127.0.0.1:6379
Error in bull queue happend: Error: connect ECONNREFUSED 127.0.0.1:6379
Error in bull queue happend: Error: read ECONNRESET
Error in bull queue happend: Error: read ECONNRESET
Error in bull queue happend: ReplyError: ERR only (P)SUBSCRIBE / (P)UNSUBSCRIBE / PING / QUIT allowed in this context

Minimal, Working Test code to reproduce the issue.

(An easy to reproduce test case will dramatically decrease the resolution time.)

bull code, index.js

var Queue = require('bull');

var videoQueue = new Queue('video encoding', 'redis://127.0.0.1:6379');

videoQueue
  .on('error', function (error) {
    console.error(`Error in bull queue happend: ${error}`);
  })
  .on('failed', function (job, error) {
    console.error(`Task was failed with reason: ${error}`);
  });

videoQueue.process(function(job, done) {

  console.log("processing video " + job.id);

  done();
});

videoQueue.add(
  {foo: 'bar'},
  {
    repeat: {
      every: 1000,
      limit: 1000
    }
  }
);

setInterval(function () {
  videoQueue.add({name:'test_task'}, {});
}, 1000);

docker-compose redis with replication
https://gist.github.com/Nikkely/ffa66e6a5a6b9019a2318bdf97d66d33

version: '3'

services:
  redis:
    image: redis:5.0.0
    container_name: master
    ports:
      - "6379:6379"
    networks:
      - redis-replication

  redis-slave:
    image: redis:5.0.0
    container_name: slave
    ports:
      - "6380:6379"
    command: redis-server --slaveof master 6379
    depends_on:
      - redis
    networks:
      - redis-replication

networks:
  redis-replication:

start redis

docker-compose up -d

start code (in other terminal)

node index.js

restart redis master

docker-compose restart redis

Bull version

bull@3.10.0

[manast]

isn't it just because since the master is down the worker simply cannot connect to redis?

[zyf0330]

#890 give a suggestion, redis option enableReadyCheck: false will let Bull resume from redis server restart.
But in this situation, repeatable job data is lost in redis and Bull won't recreate it automatically.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.