Behrad Zari
Behrad Zari
> In this scenario, it takes 2 seconds to fetch 100.000 records from Redis using .scan stream this has nothing to do with Kue > it takes almost 13 seconds...
There may be some point in code where a default `createClient` is being called on node_redis! This is a simple guess, Can you listen on error event and give me...
1) please do: ``` js queue.on( 'error', ... ) ``` 2) and stop your redis instance on localhost, so that if Kue is creating any localhost connections, you face some...
Strange! I can't figure out what is happening until you show me a code that can reproduce your situation then.
and that shows Kue is not being able to connect to your redis instance
I have upgrade node_redis lib to latest. Can you check if there's any improvements on redis connection handling in Kue 0.10?
Can you test v1 branch @mikefaraponov ?
You cannot dynamically change the concurrency in Kue, we should implement it as a new feature.
I'm thinking of doing this on a major version release, specifically 1.0.0 since it requires a very big code change, and kue redesign on redis sets/lists usage. But you currently...
when something bad fails, everything can be an issue, event with the atomic brpoplpush