A process cannot open multiple redis instances?

[jingzhiMo]

Hi, I want to create two queue in my process.But only the first queue created is useful.0

    var kue = require('kue');
    var queue2 = kue.createQueue({
        redis: {
            post: 6379,
            host: "127.0.0.1",
            db: 2,
        }
    });
    var queue3 = kue.createQueue({
        redis: {
           post: 6379,
           host: "127.0.0.1",
           db: 3,
        }
    });
    // create job
    queue2.create('test2', {x: 2}).save()
    queue3.create('test3', {x: 3}).save()

when I check the queue, the queue2 has two job. queue3 has none job; How can I create multiple queue in one process? Thanks.

[behrad]

In each process you can setup on a single redis configuration since Queue is singleton.

var kue = require('kue');
    var queue = kue.createQueue({
        redis: {
            post: 6379,
            host: "127.0.0.1",
            db: 2,
        }
    });
    // create job
    queue.create('test2', {x: 2}).save()
    queue.create('test3', {x: 3}).save()

If you want to create test2 & test3 on separate redis DB's you should use different node.js processes currently.

Kue 1.0 will change this :)

[mz3]

I have a question in the same vein - given that you set the redis connection in createQueue, how can I be sure the right redis connection is being used if I don't have a queue object and am just doing some simple maintenance with the kue object? (kue.Job.rangeByState)

[behrad]

@mz3 I'm not sure if I got your point! Kue is using a single connection for static methods like rangeByState

[mz3]

My question is given this small sample script, where would one specify the redis connection?

const kue = require('kue');
kue.Job.get(1, (err, job) => {
  console.log('removed job #1');
});

[behrad]

Currently you should initialize a Queue with kue.createQueue and send redis options before calling kue.Job.get, and Yes! this is an issue with current design. I'm creating an issue for this to be handled in Kue 1.0

[mz3]

Alright - that makes sense. Thanks so much for clarifying. Can't wait to see kue 1.0!

[poyaz]

hi, maybe this code help you multi-redis-kue

i change many file to access multi redis db (this work so good but maybe have bug)

[utsavkesharwani]

Hi,

I just came across this issue. When can we expect the new release with the fix? :open_mouth:

[BarryCarlyon]

+1 to this. Tried it today without thinking and was confused when the second queue job appeared in the first queue.

Seems the only "fix"/solution right now is to JSON API post to the second queue? (Which works for queue create which is fine for me)

But, yeah, gonna need separate processes if you wanna consume two queues. (Which matches my setup anyway)