From what I see, Kue is creating new Redis connections for every job type. We have a scenario where we have queues for each user so 200 active users with Redis connections can become an issue - especially as I don't see a way to stop processing a job type, thereby closing its underlying Redis connection.
1) Can the Redis connection be shared - from what I see, Kue cannot currently do this?
2) How can a let Kue know that it should no longer process a job type so they underlying connection to Redis is closed?
From what I see, Kue is creating new Redis connections for every job type. We have a scenario where we have queues for each user so 200 active users with Redis connections can become an issue - especially as I don't see a way to stop processing a job type, thereby closing its underlying Redis connection.
1) Can the Redis connection be shared - from what I see, Kue cannot currently do this? 2) How can a let Kue know that it should no longer process a job type so they underlying connection to Redis is closed?