-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple shards issue #56
Comments
The connector does not support clusters at the moment. If you cannot use a direct Redis connection, a possibility could be to use https://ngrok.com/. |
Thanks for the answer @manast, I found this doc
However, it isn't clear to me, it looks like the queues will be always in the same node |
Oh yes, you are right. It is not possible to specify a list of nodes in the connection at the moment, I will mark this issue as an enhancement. As you say, there is no advantage in using a cluster for BullMQ, the only reason you would need to do that is if you are using the cluster for something else and you want to reuse it for BullMQ as well. Cluster may also give you better availability guarantees, but I am not an expert on the subject. |
Hello, I'm trying to use the connector for AWS elasticache Redis (cluster mode enabled) with 3 shards/primary nodes and 3 replicas for every shard (9 nodes), but I cannot see all my queues in the dashboard connection,
When I refresh the connector, I see different queues every time, it seems like the connector is getting the queues only for 1 shard at the same time
doesn't this connector support multiple shards?
The text was updated successfully, but these errors were encountered: