[SERVER-63062] Investigate feasibility of pinning a cursor's connection in TaskExecutorCursor Created: 27/Jan/22  Updated: 27/Oct/23  Resolved: 18/Apr/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Kevin Rosendahl Assignee: Backlog - Service Architecture
Resolution: Gone away Votes: 0
Labels: servicearch-q1-2022
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Service Arch
Sprint: Service Arch 2022-2-21, Service Arch 2022-03-07
Participants:
Story Points: 2

 Description   

It may become required that connections between mongod and mongot are routed through an L4 load balancer.

We must ensure that getMores on cursors established by the search command are routed the same mongot that the initial search command was run against, and a sensible solution for this is to pin a cursor to the connection it initially used.

The current behavior of TaskExecutorCursor (which mongod uses to talk to mongot) appears to be that it acquires an arbitrary connection from its pool.

It would be helpful to know the level of work that would be required to change this to pinning the cursor. 



 Comments   
Comment by Alice Neff [ 24/Oct/22 ]

A new dependency on the Decoupled Search initiative was discovered via talks b/w Search/Siyuan/Service Architecture. New ticket here: SERVER-70777.

Comment by Matthew Saltz (Inactive) [ 31/Jan/22 ]

Whoever picks this up should first investigate what's needed for this ticket and then put it back in Needs Scheduling depending on the outcome

Generated at Thu Feb 08 05:56:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.