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.