[DOCS-11270] [Server] Large number of change streams requires large pool size Created: 30/Jan/18  Updated: 30/Oct/23  Resolved: 15/Jul/23

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Bruce Lucas (Inactive) Assignee: Ian Fogelman
Resolution: Fixed Votes: 4
Labels: quick-win, reopened, server-docs-bug-bash
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-32946 Multiple change streams cause severe ... Closed
Related
related to SERVER-42885 Registering multiple change stream wa... Backlog
Participants:
Days since reply: 1 year, 14 weeks, 1 day ago

 Description   

In SERVER-32946 we saw high change stream notification latencies due to a large number of changes, a small (default) pool size, and a low notification rate on each stream. We might want to find some place in the docs to mention this.



 Comments   
Comment by Bruce Lucas (Inactive) [ 01/Nov/22 ]

This information is needed by customers to effectively use a large number of change streams.

Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Comment by Shane Harvey [ 27/May/21 ]

Note that there is a driver-side workaround which allows many change streams to share a single connection. I've described the PyMongo workaround in this comment on SERVER-42885. Similar patterns should be possible in other drivers as well.

Comment by Bruce Lucas (Inactive) [ 31/Jan/18 ]

See this comment regarding the customer's request for improved documentation.

Generated at Thu Feb 08 08:02:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.