[SERVER-46929] Parallel consumers(subscribers) for ChangeStream Created: 18/Mar/20 Updated: 21/Mar/23 Resolved: 25/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Minor - P4 |
| Reporter: | Atil Pai | Assignee: | Backlog - Triage Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | change-streams-improvements | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Server Triage
|
||||
| Participants: | |||||
| Case: | (copied to CRM) | ||||
| Description |
|
I am R&D'ing on currently leveraging Mongo ChangeStreams. I am seeing that it has a good throughput, resilient to failures due to the 'Resume token', but I dont see any documentation on whether if/ how we can manage multiple instances of a subscriber application to receive changes in a load balance manner. Without this, we would have to use a single instance per filtered stream, inherently dealing with single point of failure. If this is currently not offered by the mongo drivers (we use scala), it would be great help if you could direct us to some other implementations that could be done to achieve this. |
| Comments |
| Comment by Carl Champain (Inactive) [ 25/Mar/20 ] |
|
If you are referring to:
There are a couple of ways you could do this:
That said, the SERVER project is for bugs and feature suggestions for the MongoDB server. As this ticket does not appear to be a bug, I will now close it. If you need assistance troubleshooting, I encourage you to ask our community by posting on the MongoDB Community Forums or on Stack Overflow with the mongodb tag. Kind regards, |