Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Load balancing JetStream consumers
See original GitHub issueHello, I am currently using JetStream and I want to know if it’s possible to load balance my consumer, similar to specifying a queue group name in normal NATS. Right now, I have 2 instances of my application running, and each time a producer publishes a message, both instances of my application receive it (both using the same push consumer with a durable name). What I am looking for is a behavior similar to queue groups, where only one of the two instances receives the message.
I was told that this is possible in the nats.go library by subscribing to the stream using js.QueueSubscribe, however, I cannot seem to find this documented with nats.js. Can someone point me in the right direction? Thanks.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@csombok I have released nats v2.0.8 which exposes the queue option.
We are facing the same limitation and for us the only viable options is using the push based subscriber with STAN. Are there any ETA for merging this PR: https://github.com/nats-io/nats.deno/pull/162? As an alternative workaround we can use patch-package to have the fix as a patch in node_modules as a temporary solution.