[DOCS-16280] Investigate changes in SERVER-57297: Support OP_MSG exhaust cursors on mongos Created: 27/Jul/23  Updated: 13/Nov/23  Resolved: 11/Oct/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 7.1.0-rc0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Minor - P4
Reporter: Backlog - Core Eng Program Management Team Assignee: Alison Huh
Resolution: Fixed Votes: 0
Labels: query, sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-57297 Support OP_MSG exhaust cursors on mongos Closed
Participants:
Days since reply: 27 weeks, 6 days ago

 Description   
Original Downstream Change Summary

mongos supports exhaust cursors. This change implements exhaust cursors for mongos when a client's getMore request has exhaustAllowed flag set.

Description of Linked Ticket

SERVER-36105 added support for OP_MSG exhaust cursors for both mongod and mongos in 4.2. Later in SERVER-44517 support for exhaust on mongos was removed in 4.4 (for the good reason that the mongos code path was untested). This ticket request that OP_MSG exhaust cursors be officially supported on mongos.

DRIVERS-535 depends on this feature since we don't want to add a feature to drivers which doesn't work in sharded clusters. The motivation is that exhaust cursors can provide better query performance.

Another potential improvement is for Load Balanced clusters. When the driver is connected through a load balancer it automatically pins the connection to the cursor. Since the connection is already pinned, it would be possible to automatically use exhaust cursors to (potentially) improve performance.


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